Architecture & CloudConference50min
Consistency Patterns in Event-Driven Architecture
This talk explains how to avoid distributed system inconsistencies caused by dual writes and rollbacks. It covers Outbox and Inbox patterns, idempotent consumers, and Sagas (orchestration and choreography), helping you choose the right pattern and understand the trade-offs of eventual consistency.
talk.summaryAiDisclaimer
Emanuel TrandafirLSEG
Distributed systems have a dirty secret. Your message broker swears the domain event is published — others are already listening, already reacting to this new order. But then, in a split second, your database rolls back. A constraint violation. Something breaks. And now the entire system knows about an order that never actually existed.
This talk covers the patterns that prevent that chaos: the Dual Write problem, Outbox and Inbox patterns for consistency between database and event stream, idempotent consumers, and Sagas — Orchestration and Choreography.
You'll leave knowing which pattern solves which problem, when to use each, and what you're really trading off with eventual consistency.
This talk covers the patterns that prevent that chaos: the Dual Write problem, Outbox and Inbox patterns for consistency between database and event stream, idempotent consumers, and Sagas — Orchestration and Choreography.
You'll leave knowing which pattern solves which problem, when to use each, and what you're really trading off with eventual consistency.
Emanuel Trandafir
I value simplicity and intentionality over blindly applying patterns and abstractions.
I care deeply about the design and testability of the software I create.
I also value communication and collaboration and enjoy sharing my knowledge through open-source contributions and technical articles.
I care deeply about the design and testability of the software I create.
I also value communication and collaboration and enjoy sharing my knowledge through open-source contributions and technical articles.