Database Architecture

Stop Chasing ‘Best of Breed’ Databases. Use Postgres for Everything.

The industry sold us on polyglot persistence—the idea of using the ‘best tool for the job’ for every workload. In reality, it’s an operational nightmare. By standardizing on PostgreSQL for everything from relational data to JSON documents and vector search, you trade marginal performance gains for massive cognitive and operational simplification. Stop chasing shiny tools and reclaim your engineering velocity.

Stop Buying Expensive Databases. S3 Already Is One.

S3 is object storage — dumb, slow, eventually consistent. Yet engineers built a fully transactional, crash-safe key-value database on top of it using LSM trees, conditional writes, and fencing tokens. The real lesson isn’t about S3. It’s that the line between “storage” and “database” is a convention you build, not a law you obey. If you understand your invariants, the cheapest substrate is often enough.