Nothing here yet.
Nothing here yet.
Mar 24 · 8 min read · I once spent three weeks in architectural meetings arguing that we should insert SQS between two Kafka topics. I wasn't doing it because I liked SQS. I was doing it because the "clean" Kafka-native retry logic felt like a complexity bomb our team was...
Join discussion
Mar 17 · 12 min read · In Part 1, we introduced a "middle ground" for Kafka retries: when a message fails, lock its key, send the message to a retry topic, and let the main partition continue processing other keys. If you need a recap, the Confluent blog covers the pattern...
Join discussion
Mar 10 · 8 min read · I was on-call when the P1 hit. Slack lighting up, a downstream team's database rejecting writes. Constraint violations everywhere. I pulled up the logs. The events looked fine. The schema was correct.
Join discussion
Feb 3 · 7 min read · SELECT * FROM my_table; Query execution time: ~5 seconds Table rows: 0 This made absolutely no sense. A few years ago, I found myself staring at a performance metric that defied logic. We had a table that was, for all intents and purposes, empty. Yet...
Join discussion
Jan 13 · 10 min read · As Go engineers, we've all internalized the context pattern. When an application shuts down, we propagate the cancellation, our select blocks catch <-ctx.Done(), and we return. Clean. Simple. Idiomatic. It usually looks like this: for { select { ...
Join discussion
