· 11 min
Rate limiting at the edge versus in the service: where each limit goes
A practical split for small teams: coarse per-client limits at the edge, per-user and per-cost limits in the service, and the 429 behaviour both must share.
11 min
Writing · 50 articles
Long-form notes on designing, securing and running production systems, mostly on Google Cloud. Every article is written from a real decision, with the trade-offs and the numbers behind it. Filter by topic, or start with the newest.
· 11 min
A practical split for small teams: coarse per-client limits at the edge, per-user and per-cost limits in the service, and the 429 behaviour both must share.
11 min
· 10 min
How a small team can keep Terraform state safe: a versioned GCS backend, locking you can trust, and a state layout that limits the damage of a bad apply.
10 min
· 12 min
Which Postgres schema changes lock a table, which are safe, and the three-release pattern I use to change a live column without an outage or a long window.
12 min
· 9 min
Most small teams should not start with a service perimeter. The organization prerequisite, the friction it adds, and when it pays for itself.
9 min
· 11 min
Thirty well-chosen cases, deterministic checks first and a model judge last, run several times per case. A practical eval setup a single developer can maintain.
11 min
· 9 min
Most incident reviews end as documents nobody opens again. A one-page format, actions filed as ordinary issues and a thirty-day check make change likely.
9 min
· 11 min
A nonce gives a strict script policy but ends static rendering; a static header keeps pages cached but needs unsafe-inline. How to choose on a Next.js 16 site.
11 min
· 8 min
Pin base images by digest and let a bot move the pin. Why that beats floating tags and manual bumps, with a multi-stage Dockerfile and a CI scan.
8 min
· 11 min
A jobs table, one claiming query and a lease column give a small team a reliable work queue on the Postgres it already runs. What to build, and where it stops.
11 min
· 9 min
Ordering keys give per-key order and take away parallelism. Learn what they guarantee, how one failure stalls a key, and when versioned events are a better fix.
9 min
· 12 min
Batch work behaves badly behind an HTTP endpoint. Compare Cloud Run jobs and services on retries, parallelism and exit codes, and shard work across tasks.
12 min
· 11 min
A Firestore rules deploy replaces everything at once, with no canary. The traps in the rules and the release path, and the pipeline that catches them.
11 min