Skip to content

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.

, 8 min read

Why the second version of an event-driven design is usually the simpler one, and the retry question that decided the whole shape.

Filed under

  • Building
  • Kafka

Related

  1. System design, , 9 min read

    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.

    • Messaging
    • Kafka
    • PostgreSQL
  2. System design, , 11 min read

    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.

    • Messaging
    • Kafka
    • RabbitMQ

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