Posts
All the articles I've posted.
Idempotent MERGE: the re-run was safe, so why did the totals change?
Merging on a natural key is supposed to make a batch job replayable. It does, right up until the source batch, the ordering, or the input window stops being what you assumed.
At-least-once delivery means your consumer will process the same event twice
SQS, Kinesis, and DynamoDB Streams all guarantee at-least-once. That guarantee is a requirement on your consumer, not a promise you can ignore.
A 90% cache hit rate and the API is still slow. Look at your connection pool.
Caching removes repeated work. Connection pooling removes per-request setup. They fix different halves of your latency, and a cache cannot touch the half it doesn't own.
Why MySQL says "Unknown column" for an alias you just defined
You aliased a column in SELECT, used it in WHERE, and got ERROR 1054. ORDER BY accepts the same alias without complaint. Here's the one rule that explains both.
You created an index and the query is still slow. Here's why MySQL ignores it.
EXPLAIN says type: ALL and key: NULL even though the index exists. Four common reasons an index you just built gets skipped, and how to confirm which one you hit.
Your WHERE <> filter is silently dropping every NULL row
WHERE role <> 'TA' looks like it means everyone who isn't a TA. It means everyone we know for certain isn't a TA. Nothing errors, the result is just short.