From 30 Minutes Down to 10: Taming our Monolith's CI Build Times
When Cash App was originally developed we had a single service powering all backend functionality, codenamed “Franklin”.
Showing 5 of 5 articles (Page 1 of 1)
When Cash App was originally developed we had a single service powering all backend functionality, codenamed “Franklin”.
This is the final post of a three part series. In part one, we discussed the performance problems that we found with our activity feed and some of the changes we made to the way we use dispatch queues.
This is the second post of a three part series. In part one, we discussed the performance problems that we found with our activity feed and some of the changes we made to the way we use dispatch queues.
This is the first post of a three part series discussing recent performance improvements we made in our iOS app.
The Cash App Android app uses presenters because they’re easy to write, easy to review, and result in boring code that just works.