Postgres Until It Hurts: The Operational Case for One Database Doing Several Jobs
The pendulum swung back to one relational database for documents, queues, search and vectors: the case for it, and where a specialised system still wins.
6 min read
3 posts, newest first.
The pendulum swung back to one relational database for documents, queues, search and vectors: the case for it, and where a specialised system still wins.
6 min read
Sharding usually arrives years early and charges rent forever in lost joins, transactions and simplicity. What to exhaust first, and the signals that it's time.
6 min read
Deploys taught us every change is reversible. Schema and data migrations are not, and teams discover which step was one-way during the incident it caused.
6 min read