Communicating between two Bounded Contexts in DDD

by

When integrating BCs, you have a few options. The reason that calling out to an external BC is discouraged is because it requires for both BCs to be operational at the same time. However, this is often quite acceptable and is simpler than the alternative. An alternative is to have the Game BC subscribe to events from the User BC and keep local copies of the data it needs, which in this case is information about whether a user is a group leader. In this way, when the Game BC needs to determine whether a user is a group leader, it doesn’t need to call out to the User BC, it just reads locally stored data. The challenge of this event-driven alternative is synchronizing the events. You have the make sure the Game BC receives all appropriate events from the User BC. Another challenge is dealing with eventual consistency, since the BCs may be slightly out of sync at any given point in time.

CQRS is somewhat orthogonal to this problem.

More Related Contents:

  1. What are the benefits of Persistence Ignorance?
  2. Is it ok for entities to access repositories?
  3. Where do I find some good examples for DDD? [closed]
  4. Value vs Entity objects (Domain Driven Design)
  5. Refactoring code to avoid anti-pattern
  6. How are Value Objects stored in the database?
  7. Multiple Aggregates / Repositories in one Transaction
  8. How to handle set based consistency validation in CQRS?
  9. Aggregate Root references other aggregate roots
  10. EF codefirst : Should I initialize navigation properties?
  11. Who should handle the conditions in complex queries, the data mapper or the service layer?
  12. Domain Driven Design: Domain Service, Application Service [closed]
  13. What is the difference between DAO and Repository patterns?
  14. Using Kafka as a (CQRS) Eventstore. Good idea?
  15. Should services always return DTOs, or can they also return domain models?
  16. Persist Data by Programming Against Interface
  17. Should I abstract the validation framework from Domain layer?
  18. How to remove unit of work functionality from repositories using IOC
  19. DDD – the rule that Entities can’t access Repositories directly
  20. The repository itself is not usually tested?
  21. MVVM: Binding to Model while keeping Model in sync with a server version
  22. ASP.MVC: Repository that reflects IQueryable but not Linq to SQL, DDD How To question
  23. Get all associate/composite objects inside an object (in Abstract way)
  24. How to pass Current User Information to all Layers in DDD
  25. IQueryable & Repositories – take 2?
  26. DDD Approach to Access External Information
  27. POCO’s, behavior and Peristance Igorance
  28. Polymorphism: Is ORM entity a Domain Entity or Data Entity?
  29. DDD, Anti Corruption layer, how-to?
  30. Why does the entity framework need an ICollection for lazy loading?

Leave a Comment