Database
PostgreSQL at scale
Operating PostgreSQL when the dataset and write rate stop fitting on a single instance — partitioning, replication, vacuum tuning, and the managed-service landscape.
PostgreSQL is now the default database for most new applications; the operational complexity of running it at scale used to be a major drawback, but the managed-service ecosystem (Aurora, AlloyDB, Neon, Supabase, RDS) and the extension ecosystem (Citus, TimescaleDB, pgvector) have closed most of that gap.
Notifire's coverage tracks the releases and tooling that change the cost-or-complexity curve: logical replication maturity, partition routing, vacuum behaviour under high write load, and the connection-pooling layer (PgBouncer, pgcat) that sits in front of nearly every production deployment.