Topic · 2 posts

Databases

Most performance bugs live in the database. Notes on EXPLAIN output you can defend, indexes that earn their disk, replication topologies that survive failover, and when to stop scaling vertically.

Diagram showing B-tree node insertion representing database index structures, hero image for database posts.

The database is usually the slowest thing in the request path, the most expensive thing to get wrong in a migration, and the most load-bearing thing in the incident blameless post-mortem. Everything under this hub comes from the boring side of that - query plans, indexes, locks, and the operational reality of Postgres at scale.

§ Writing

All writing on databases

§ Related

Other topics