May 27 · 21 min read · Opening a new database connection for every query is one of the most expensive things your backend can do. Connection pooling is how you stop doing that. Why connections are expensive Most developer
Join discussion
May 10 · 5 min read · If you are building full-stack applications on the edge using Cloudflare Workers (or Cloudflare Pages) and connecting to a PostgreSQL database, you have likely encountered the dreaded 500 Internal Ser
Join discussion
May 9 · 14 min read · Originally published at theculprit.ai/blog/sql-primitives-for-incident-split-merge. Every alert-correlation system gets things wrong. The interesting question is what the on-call engineer can do about it at 2 a.m. The bad answer is: nothing. The sys...
Join discussionMay 7 · 12 min read · Thesis A "no mocks" testcontainers policy caught two production-fatal Postgres bugs in one test run. The first would have shipped silently and failed at runtime on every fresh tenant. The second would have shipped to staging and waited there for a re...
BBaoDev commentedMay 2 · 9 min read · Every backend developer has written this line a thousand times: SELECT * FROM orders WHERE user_id = $1 And this one: DELETE FROM invoices WHERE id = \(2 AND user_id = \)1 And somewhere, deep in the
Join discussion
Apr 30 · 7 min read · A frontend QA pass on a brand-new account opened the library sidebar and saw two notes I had never written. They were public seed entries from a different user. Same UUIDs across every fresh account I tested. This is a post-mortem of how multiple Pos...
BBaoDev commentedApr 30 · 10 min read · The first time I broke production with a migration, I was running a NOT NULL constraint on a 12-million-row users table during peak traffic. The query locked the table, the API timed out, payments failed, and I spent the next 90 minutes hunched over ...
Join discussion
