Domain driven design vs event driven design

Events are useful as the communication mechanism between different bounded contexts.

She talked about two important components of event driven microservices: Commands and Events. It can also be split according to business processes in the system.ДЄlagarsamy discussed how bounded contexts communicate with each other, using the example of an Airline application. She suggested that domain models can be split according to teams and departments to help with a better organization of the model.

Shipping: It's a thing that has weight and dimensions that needs to be packagedД¬reating unified models are hard, and finding the right boundaries between the business domain can be a challenge.

Inventory: It's a thing that is either available or not.

Sales: It's a thing that has a description, images, and a price.

The product entity is context-based, and means different things to different domain teams as follows:

She discussed an example use case of an e-commerce application where the 'product' is one of the core entities. Bounded contexts provide clarity, and the models in each bounded context are logically consistent and can evolve freely. Indu Alagarsamy recently spoke at the QCon New York 2019 Conference about using the combination of well-defined bounded contexts and events to develop autonomous microservices that are flexible to adapt to the business changes.ДЄlagarsamy said when you start to use the technology of messaging to communicate between clean and well-defined bounded contexts, you can remove temporal coupling. Domain-driven design (DDD) concepts like bounded contexts and messaging can be used to build reliable systems that can scale with the business changes.

Domain driven design vs event driven design