rcmnd

Cash AppCompany

Block's mobile payments and banking app

7 things

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

2025-03-11·code.cash.app ↗

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

2023-06-06·code.cash.app ↗

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

2025-11-18·code.cash.app ↗

Kotlin MultiplatformSoftware

recommended

In 2021, we adopted Kotlin/JavaScript for shared presentation logic in our clients.

Cash App's Summer of Kotlin Multiplatform kickoff

2023-06-06·code.cash.app ↗

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

2025-03-11·code.cash.app ↗

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

2023-10-23·code.cash.app ↗

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

2023-10-23·code.cash.app ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.