Rebuilding the billing flow as events
Why the second version of an event-driven design is usually the simpler one, and the retry question that decided the whole shape.
Related
Keep reading
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.
Designing a URL shortener
The classic interview system, built small and measured: where the reads go, what the cache is for, and the one decision that made everything else easy.
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.
Next
Something here worth a reply?
If this entry raised a question, or you think I have got something wrong, I would much rather hear it than not.
Get in touch