The lesson
Start with the external event that broke the old system, then make the database choice feel urgent and practical.
The story opens with Kami’s origin, its education market context, and the pandemic moment that forced remote learning. A summary card states the move from Postgres to CockroachDB and gives headline facts including “USERS 30 M,” “GROWTH 20 x,” “COUNTRIES 180 +,” and “MONTH MIGRATION 4.” The body follows the pressure in order: “Forecasting growth & a storm ahead,” “Trusting a famously resilient creature: CockroachDB,” “Executing a live migration,” and “What’s next for Kami,” with Jordan Thoms quotes explaining the tradeoffs.
Don't copy Kami’s pandemic education context, Hacker News discovery, or the CockroachDB creature joke. Keep the structure of external pressure, old-system limits, evaluation tradeoffs, migration method, and customer-owned outcomes.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.