This section provides an overview of what domain-driven-design is, and why a developer might want to use it.

It should also mention any large subjects within domain-driven-design, and link out to the related topics. Since the Documentation for domain-driven-design is new, you may need to create initial versions of those related topics.

A bounded context is subset of a large domain model. In larger domains, multiple teams will be working on multiple areas of the solution and this strategic pattern helps to share the work among the teams. The idea is to divide the big domain model in more focused areas, giving the team the freedom to solve each subset of the domain in the best way, even, with totally independent code, database and services.

For example, it's possible to have one project addressing customer targeting, a second project targeting sales management and a third project managing the warehouse. The idea is to have independent teams working in parallel on different areas of the domain. There must be some kind of agreement on how to communicate between each bounded context.