Platform · 1974–now · Foundations
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.
Why SQL / Relational stuck
Relational algebra was math, not marketing — joins and transactions solve real business invariants. Every NoSQL wave eventually rediscovered constraints under a new name. SQL stuck because wrong data costs more than any license fee.
Case studies
- Deutsche Bank absorbs Postbank into integration purgatory — Multi-year, multi-billion IT integration; branch and core systems lagged for a decade
- Enterprise blockchain pilots that never left the lab — Eight-figure innovation budgets; production traffic near zero
- Startup rebuilds on NoSQL, rediscovers joins — 18-month rebuild; doubled headcount for data consistency work
- Low-code to replace engineering — then hire engineers — Seven-figure platform licenses; shadow IT integration debt
Compare with
Related
Practice · 2009–2019
NoSQL for Everything
Schema-optional databases sold as a lifestyle. Right tool for some jobs; default for none.
$ Startups ditched Postgres for document stores "because scale," then rebuilt relational integrity in application code — and paid twice when joins came back as a product requirement.
Practice · 2005–now
ORM-as-database
Hide SQL until N+1 queries own your night. Good ORMs survived; "never write SQL" didn't.
Platform · 2009–now
Redis
Fast structures in memory with persistence options. Cache, queue, session store — pick your footgun.
Platform · 1996–now
PostgreSQL
The open-source relational default — JSON, extensions, and enough correctness to survive every NoSQL wave.