Microservice architecture borrows many classical concepts. Bounded Context is one of the most important ideas of domain-driven design.
A context means specific responsibility. Bounded Context implies a responsibility with explicit boundaries.
Reading from a few blogs, the bounded context means more of real-world identification of responsibilities. It’s seeing things from different altitudes: An application is a bounded context. A level below, it’s UI, backend are BC.
Overall, seeing a BC as a cell (like an organic cell) came more naturally. A cell defines a specific set of responsibilities. It has an explicit interface to accept/ reject model (communication data) requests.
Why Bother Bounded Context
- BC promotes loses coupling and high cohesion.
- Building Microservices by Sam Newman
Written with StackEdit.