Designing a notification system
Fan-out, user preferences and the retry budget — sketched end to end before building any of it.
Fan-out, user preferences and the retry budget — sketched end to end before building any of it.
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.
Sharding vs partitioning
Two words used interchangeably in meetings, and the operational difference that makes them not the same thing at all.
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
Have a system worth arguing about?
If this note raised a question, or you would have designed it differently, I would like to hear it.
Start a conversation