![distributed domain driven design distributed domain driven design](https://docs.microsoft.com/en-us/azure/architecture/microservices/images/monolith/figure2.png)
![distributed domain driven design distributed domain driven design](https://blackwells.co.uk/jacket/l/9780136928638.jpg)
DISTRIBUTED DOMAIN DRIVEN DESIGN SOFTWARE
In order to do that, he will comunicate with each bounded context using the dedicated queue of the bounded context and creates it if it does not exits.Įach BC is bound to this specific queue, and add the event coming from outside in its own event store, and afterwards project it to its own projection.A curated list of Domain-Driven Design (DDD), Command Query Responsibility Segregation (CQRS), Event Sourcing, and Event Storming resources.Ĭheck out my blog and weekly DDD newsletter or say hi on Twitter!ĭomain-Driven Design (DDD) is an approach to software development for complex needs by connecting the implementation to an evolving model. He is also responsible to handle the "sagas" and can send corrective actions to each bc. He is the one reading the bandMasterQueue and decides which events are public and which are not. The bandMaster "bounded context" knows about every different BCs he looks after. If it would fail on step 2 because of no rabbitmq available, then I expect my event store to try again to dispatch the message to the RabbitMQ after sometime (not really though precisely about this part, I must say.) publish this event to the queue BandMasterQueue.Each projection has a little tiny store of events already projected to warrant idempotency over some period of time. project on itself this event to every little projection.When producing an event, the event store stores it and its dispatch consists of two steps : Therefore, I was thinking about having each of them referencing a queue : BandMasterQueue
![distributed domain driven design distributed domain driven design](https://ars.els-cdn.com/content/image/3-s2.0-B9780128054673000041-gr001.gif)
If a bounded context is not available the messages, that it should receive, must wait patiently for its return ie : every event published must be forwarded at least once to all the bc interested.The bounded context must not be hindered if the other bounded context are down or if rabbitMQ is down.The bounded context must not know about each other.In order to make these bounded context talk to each other I was planning on using Rabbit MQ. I am on my way to create an application with 4 bounded context using CQRS & event sourcing.