Bounded Context Caching will solve the problem of too long response times technically.When domain-driven design and strategic design define the structure of the overall system (section. The patterns required from domain- driven design were introduced in section 3.3. Each microservice can have a DDD domain model. Domain-Driven Design Domain-driven design (DDD) is one way to internally structure microservices.Often architects develop a microservice architecture.
A key element is that the microservices are distributed into contexts-that is, areas that represent separate functionality. Strategic Design and Domain-Driven Design Section 3.3 discussed the distribution of microservices based on strategic design, a concept taken from domain-driven design.One team can work on one or several Bounded Contexts, which each serve as a foundation for one or several. Such a model can be designed based on Bounded Context. Bounded Context and Microservices Each microservice is meant to model one domain so that new features or changes have only to be implemented within one microservice.Customer/Supplier means that a subsystem offers a domain model for the caller.
In case of a Shared Kernel the domain models share some common elements however, in other areas they differ.Collaboration between Bounded Contexts How are the individual Bounded Contexts connected? There are different possibilities:.The component Delivery implements the delivery process. The component Order is responsible for the order process. The different Bounded Contexts are Order, Delivery, and Billing. Bounded Context: An Example The customer from the e-commerce system shall serve as an example for a Bounded Context (see Figure 3.4).
(Microservices Flexible Software Architecture) This aspect of DDD is probably even more important than the building blocks. DDD describes, along with strategic design, how different domain models interact and how more complex systems can be built up this way.