In my previous article, I did a detailed discussion about bounded context and how to tackle the complexity of a domain. It is best to divide the domains into several subdomains and map them with different bounded contexts where each business entity/value object has a certain meaning in that context, so every stakeholder of the business (product owners, developers, architects, and sponsors) understand the context and refer to entities with the proper taxonomy. There should be no confusion about naming when we discuss domain objects basis in context with a ubiquitous, unified language among business stakeholders.
With bounded context, we properly define a business model, create a different context based on the business domains, but always a functionality spans over multiple business entities , and those entities lie in the different Bounded contexts/domains, so it is utmost important to understand the relationship between the Bounded contexts, to architecting the business solution Context Map is a technique by which we can visualize the relationship between different contexts and Integration architect choose the best integration patterns to communicate to other contexts.
from DZone.com Feed https://ift.tt/2kAkYpR
No comments:
Post a Comment