· 14 min
Connection pooling when every service is tiny
Twelve small Cloud Run services, each with a sensible pool, can still exhaust one Postgres. How to do the connection math and pick a pooler.
14 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.
· 14 min
Twelve small Cloud Run services, each with a sensible pool, can still exhaust one Postgres. How to do the connection math and pick a pooler.
14 min
· 15 min
A scheduled sync pays to refresh every record, including the ones nobody reads. Refreshing stale data when someone looks makes cost follow attention.
15 min
· 13 min
Per-service path fragments, a small Node generator that enforces the rules humans forget, and a CI check that keeps the API Gateway config honest.
13 min
· 12 min
JSON logs that Cloud Logging understands, correlated by trace, with the noise excluded before it is billed. A pino setup for Cloud Run and what it costs.
12 min
· 13 min
A dead-letter queue turns a stuck message into a ticket instead of an outage. How to set one up on Pub/Sub, alert on it, and replay safely after a fix.
13 min
· 13 min
A layered CLAUDE.md, tight permissions, hooks, skills and scoped MCP servers: the setup that keeps Claude Code safe and cheap across dozens of repositories.
13 min
· 15 min
Measure which phase of a Cloud Run cold start is slow, match it to the lever that shortens it, and pay for warm instances only where the latency earns it.
15 min
· 13 min
Nine traps in Node config and Secret Manager on Cloud Run, from silent fallbacks to a trailing newline, each with the symptom, the cause and the fix.
13 min
· 12 min
Firestore is superb at keyed reads and poor at friends-of-friends. When a graph database earns its place, and how to keep two stores honest.
12 min
· 9 min
How I structure Google Cloud IAM so people get access through groups, workloads get one keyless service account each, and every grant is small and auditable.
9 min
· 13 min
Pub/Sub will deliver some messages twice, and that is by design. Here is how to build consumers whose side effects happen once anyway, with working code.
13 min
· 15 min
Every upstream call spends money and quota. A layered defence of validation, rate limits, caching, single-flight and leases keeps both under control.
15 min