Idempotent consumers, without the ceremony
What actually happens when the same message arrives twice, and the smallest set of changes that makes a consumer safe to retry.
Why the boring architecture usually wins
Queues, boundaries and failure modes: distributed systems, databases, messaging, caching and scaling.
All notes
Sharding vs partitioning
Two words used interchangeably in meetings, and the operational difference that makes them not the same thing at all.
Redis caching: the invalidation I got wrong first
Cache-aside looked simple until two writers raced. What I changed, and what I would measure before adding a cache next time.
RabbitMQ vs Kafka
Not a benchmark. A comparison of the questions each one makes you answer: about ordering, replay, consumers and who owns the offset.
Designing a notification system
Fan-out, user preferences and the retry budget — sketched end to end before building any of it.
Next
Have a system worth arguing about?
I am always up for a conversation about architecture, trade-offs, or a bug that refuses to die.
Start a conversation