Domain Driven Design Bounded Context Microservices
Bounded contexts and microservices are similar but from my understanding a bounded context can consist of several microservices.
Domain driven design bounded context microservices. Bounded context is a very important term in microservices. Vaughn vernon s implementing domain driven design focuses on strategic design from the outset. First let s understand the meaning of the word context. Domain driven design defines bounded contexts as the setting in which a word or a statement appears that determines its meaning.
These result from the architectural principles of the domain driven design and devops. Microservices is an architecture design model with a specific bounded context configuration and dependencies. Bounded context opens part iv strategic design. I would try to explain bounded concept in a very simple and clear manner.
In the book domain driven design eric evans describes several patterns for maintaining the integrity of a domain model when it interacts with another bounded context. Understanding the bounded context helps us form autonomous teams and by extension autonomous microservice. Sam newman a recognized promoter of microservices and author of the book building microservices highlights that you should design your microservices based on the bounded context bc pattern part of domain driven design as introduced earlier. Chapter 2 talks in detail about how a domain is divided into bounded contexts and chapter 3 is the best source on drawing context maps.
Sometimes a bc could be composed of several physical services but not vice versa. Then i would provide an example. The bounded context is a key design pattern borne out of domain driven design or ddd. Arguably one of the most difficult microservices patterns to apply and implement is the bounded context.
One of the main principles of microservices is that services communicate through well defined apis. Bounded context and microservices.