How To Choose A Database For Your Ledger
by The Payments Engineer Playbook Store
$24.99
You don't have a database problem. You have a decision-making problem.
Most engineers building money software reach for PostgreSQL because it's the one they know, not because it's the right fit. And it works, up to a point. Then a hot settlement account makes every payment wait on the same row, the append-only table passes a billion rows, the overnight reconciliation doesn't finish before sunrise, and a single write region starts declining customers on the other side of the world.
Ledgers aren't ordinary software. They never delete anything. They have to be correct to the cent. And a handful of accounts take most of the traffic. A ledger with those properties needs a database chosen on purpose, not out of habit.
This book shows you how to make that choice. You'll learn:
- How Uber's DynamoDB ledger cost an estimated $8 million, and why incentives, not technology, were to blame
- Why even TigerBeetle, a database built for ledgers, struggles to move money across currencies
- Three questions that tell you which open-source databases will keep their promises
- A survey of exotic databases that could be a better fit for your ledger, what you give up to get them, and what will feel uncomfortable once you adopt them
You may still end up choosing PostgreSQL. If you do, it will be an informed decision.
Alvaro Duran writes The Payments Engineer Playbook, the only newsletter tailor-made for engineers of money software. More than 2,000 engineers at companies like Stripe, Coinbase and Modern Treasury read it every week.