Practice · 2009–2019 · Cloud Scale
NoSQL for Everything
Schema-optional databases sold as a lifestyle. Right tool for some jobs; default for none.
Why NoSQL for Everything became a costly fad
NoSQL-everywhere failed because ACID and joins are business requirements wearing a schema. Teams paid twice: once to skip migrations, again to rebuild them in services. The fad was confusing Facebook's problem with yours.
Cost of the fad
What NoSQL for Everything cost
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.
Case studies
Patterns
Compare with
Related
Platform · 1974–now
SQL / Relational
Declarative data that outlived every ORM fashion cycle. Postgres and friends keep winning by being boring.
Platform · 2009–now
MongoDB
Document DB that became a punchline, then a grown-up product. Survived by getting serious about transactions and ops.
Platform · 2010–now
Elasticsearch
Full-text search and log analytics at scale. Powerful, hungry, and everywhere in observability stacks.