The Payments Engineer Playbook

The Payments Engineer Playbook

Home
Glossary
Archive
About

databases

Why Low Cardinality Accounts Are A Ledger's Bottleneck
You can build a ledger that’s blazingly fast with a slow programming language.
 • Alvaro Duran
TigerBeetle's Stablecoin Mistake
Is there such a thing as "the ultimate fintech database"?
 • Alvaro Duran
From Stock Markets To Ledgers, Part VI: Mechanical Sympathy
3 books to satiate your curiosity and ambition
 • Alvaro Duran
Raft Consensus in 2,000 words
Understanding the Understandable Consensus Protocol
 • Alvaro Duran
How To Prevent Cache Stampedes
Think cache invalidation and naming things are hard?
 • Alvaro Duran
What Makes DynamoDB a Good Database Choice for Payments
A database engine for the always-on payments era.
 • Alvaro Duran
The ID Gapless-Latency tradeoff
You can get unique identifiers at scale either by Coordinating or by Centralizing ID creation. But you can't get gapless sequences without having to…
 • Alvaro Duran
Database Migration Wartime Stories
And some PostgreSQL not-so-well-known lock workarounds
 • Alvaro Duran
NoDB: Processing Payments Without a Database
Making payments simpler and more reliable by removing databases out of the way.
 • Alvaro Duran
Consistency, Availability, Prowess: How Stripe and Shopify push the limits of distributed payments
Changes on the infrastructure, noticing what the CAP theorem really means, and scaling like crazy.
 • Alvaro Duran
How to build 99.999% uptime payment systems
In order to keep pace with state-of-the-art, money software must work for all possible databases
 • Alvaro Duran
How Modern Treasury Invented Event Locking
Race conditions are the nastiest problem in money software. They've forced engineers to make wrong design choices. Not anymore.
 • Alvaro Duran
© 2026 Alvaro Duran Barata · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture