3 min read
PostgreSQL patterns for applications that grow
Connection pooling, index discipline and migration safety: the three things that decide whether a Postgres-backed application scales quietly or loudly.
- Data
- PostgreSQL
- Performance
Insights
Positions we hold and apply on client work, written for engineers and technical decision-makers. Each one is specific enough to act on, and to disagree with.
3 min read
Connection pooling, index discipline and migration safety: the three things that decide whether a Postgres-backed application scales quietly or loudly.
4 min read
Most accessibility failures in enterprise applications are engineering decisions, not design decisions. Here is where they actually originate.
4 min read
Integrations fail on the far side of a boundary you do not control. Idempotency, retries with backoff, and observability are what make that survivable.
3 min read
A rewrite discards working behaviour nobody wrote down. Here is the test we apply before recommending one, and what incremental modernisation looks like instead.
4 min read
The three protocols solve different problems. Picking by familiarity rather than by problem is the most common and most expensive identity mistake.
If one of these described your system a little too accurately, that is usually a good reason to have a conversation.