Event-driven architecture: Outbox pattern and its implementation options

Message brokers, like Kafka and RabbitMQ, have become central components of many modern architectural solutions. You can barely find any commercial product without asynchronous data exchange.


Imagine that, as a systems analyst in a product development team, you encounter a problem: messages sent by one of your microservices getting lost and not reaching their destination. As a result, the product's quality suffers.


If you're unsure how to solve this problem, you'll find my talk interesting.


In my talk, I will explain the Outbox pattern, which ensures reliable asynchronous data exchange between microservices, preventing message loss.


My talk is straightforward — no vague and ambiguous statements. You will learn how to implement the Outbox pattern in its classic form and with Kafka Connect (for those who like to experiment).


As a result, you'll have new neurons and knowledge that you can use to improve the quality of your system's architecture.

Comments ({{Comments.length}})
  • {{comment.AuthorFullName}}
    {{comment.AuthorInfo}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to

or
Chat with us, we are online!