9 articles
New payment confirmation code ran in production on Joytop for a week in shadow mode — deciding nothing, only watching. Tomorrow it becomes the one that decides. What shadow mode actually does, what it protects against, and why you can't turn it on without watching it.
A retry is not a duplicate request — until it is. How idempotency keys actually work, why the naive version still double-charges, and the exact Postgres constraint that makes the guarantee real.
Node 24 strips types at runtime, so `node server.ts` just works. That is genuinely useful — and it is not the same thing as Node supporting TypeScript. Here is where the line actually falls.
The joke says it's one of the two hard problems. The reality is that most teams never write an invalidation strategy at all — they write a TTL and hope. Here is what the alternatives actually cost.
Async I/O and a built-in uuidv7() were the headline features. One of them quietly fixed a problem I had been working around for two years; the other did less than the benchmarks promised.
You added the index, ran the query, and it is still slow. The planner is not ignoring you — it is telling you something about your data, your column order, or your types. Here is how to read what it says.
A deploy restarted the workers mid-flight and the emails were simply gone. What it takes to build a queue where a dead process is a delay, not a data loss.
Every payment provider tells you to make your webhook idempotent. Almost nobody tells you what that actually requires — which is a decision about identity, a decision about state, and a place to put the evidence.
Tenant isolation held together by developer discipline will eventually fail, because it only takes one query. Here is how to push the boundary down into Postgres so forgetting stops being possible.
