![]() Care context contains patient related concepts, like care activities and care documents.In a healthcare system Care and Organization are two bounded contexts. So, what I do is I implement bounded contexts with C# namespaces and enforce the boundaries between them with a static code analyzer tool called NsDepCop. Changing physical boundaries is much more costly then changing logical ones so you should postpone the physical slicing until context bounderies are well understood, tried and tested. Especially not in the early stages of a system’s development when models and context boundaries are not fully understood and can change a lot. People often think of bounded contexts as physical components (e.g.: separate web services) because the physical separation encourages loose coupling and forces an explicit model mapping between the components.īut wait, logical dependency and model mapping concerns should not dictate physical packaging decisions! There are many other forces that shape the physical packaging decisions so (logical) context boundaries should not be a primary concern here. As a boundary it helps you to decompose the problem into smaller, more manageable units whose interdependence in minimized and controlled.E.g.: a Product in the Warehouse Context has properties like size and dimensions while in the Sales Context it has price and sales tax rate. ![]() As a context it defines the precise meaning of a concept. ![]() In domain-driven design (DDD) a bounded context is used both to disambiguate concepts and to manage complexity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |