Messages between bounded context By David Boyne
Messages between bounded context By David Boyne
Struggling with event-driven architecture?
You're not alone. I've seen plenty of teams start with a clean event-driven architecture only to end up with a distributed big ball of mud — broken schemas, unclear ownership, events nobody documented. There's two ways I can help:
When sending data between bounded context you have a few options to handle the data/contracts.
Conformist Pattern
- System A sends data to System B. System B does no translation of the data before using it within it’s bounded context.
- System B conforms to the data/contract.
Anti-Corruption Layer
- System B does not want to conform to the contract of System A.
- System B translates the data into a domain model it can understand.
Open-Host Service
- System A sends data to System B but translates it before it is sent.
- Public language is used between systems.
- Integration details of System A is still locked away, but public inteface/message exposed.
Extra Resources
- Learning Domain Driven Design - Notes taken from the book “Learning Domain Driven Design” by Vladik Khononov.
Explore other visuals
Want to work together?
If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.
EDA Visuals: The book
Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer.
This book contains all the visuals in one book, you can download, read offline and explore.
If you would like to support my work, you can purchase the book. This helps keeping the visuals free for the community. Purchase the book
