PlanetScaleService PlanetScale
loved
Moving to PlanetScale was a game changer for the team, as we historically run pretty light, and time previously spent maintaining a fairly large bespoke architecture can now be spent on developer experience tooling that makes current and future developers’ lives easier.
Cash App moving its Vitess fleet from its own datacenters to PlanetScale
code.cash.app ↗·2025-03-11Wrong?
KotlinSoftware
loved
At Cash App we use Kotlin on all of our platforms.
Cash App on its Kotlin adoption timeline across Android, backend and iOS
code.cash.app ↗·2023-06-06Wrong?
MetroSoftware
recommended
Evaluations done by Cash and Square teams convinced us that Metro is well aligned with our long term vision for dependency injection, and therefore we decided to adopt it.
Why Cash Android migrated its dependency injection from Dagger and Anvil to Metro
code.cash.app ↗·2025-11-18Wrong?
Kotlin MultiplatformSoftware
recommended
In 2021, we adopted Kotlin/JavaScript for shared presentation logic in our clients.
Cash App's Summer of Kotlin Multiplatform kickoff
code.cash.app ↗·2023-06-06Wrong?
VitessSoftware
uses
Our solution to managing this kind of capacity has been to utilize Vitess, as a piece of middleware that sits in front of hundreds of otherwise normal MySQL instances, handling the hard work of figuring out what query traffic routes where.
Cash App on running its largest databases on Vitess
code.cash.app ↗·2025-03-11Wrong?
MySQLSoftware
uses
Because many schema changes in MySQL are blocking, the accepted workaround for many years has been to use an external tool such as pt-online-schema-change or Gh-ost .
Cash App on running schema changes against MySQL at scale
code.cash.app ↗·2023-10-23Wrong?
gh-ostSoftware
mixed
Gh-ost was designed in a time when MySQL replication was single threaded. As a direct consequence of this, it itself is only single threaded.
Why Cash App built its own online schema change tool instead of continuing with gh-ost
code.cash.app ↗·2023-10-23Wrong?