DDD study notes - the field, subdomains and bounded context

In poorly designed software, the sub-domains and bounded context (context) is difficult to-one mapping relationship. - description better design, sub-domain bounded context and it should be one to one mapping relationship.

The same or similar name object exists in different models, but they lack a different meaning. When surrounded by a boundary model is displayed, wherein the meaning of each is determined by the concept. The main context is bounded on the boundary of a semantic, we should measure the use of a context bounded by the correctness of this.

Do not try to create a large and comprehensive software model, where each concept is only one meaning in the global range. Projects are too large, too complex, we can not be together all the stakeholders, not to mention the agreement. So our best way to address this is different, then the context of bounded model separation art.

Bounded context is not intended to create a single project assets, it is not a separate component, document, or a block diagram. So he is not JAR or DLL, but these can be used to deploy bounded context.

Bounded context mainly used to package the common language and art objects, but also contain those elements provide an interactive means and auxiliary functions of the domain model.

The size of the bounding context, may comprise a base part number in the domain model: module, aggregation, field events, field services? Principle is fitting, not much

less.

To create a right of bounded context is not a simple matter.

The model can be likened to music, in which the number of notes (module, aggregation, events and services) should be just as much design is required.

We create effects of incorrect size bounded context factor: 1 with a framework to guide the design and development, rather than common language. This time we usually would from a technical rather than semantic boundaries to consider the issue. The development tasks assigned to split bounded context.

Not just to create a context bounded architectural component developer or resource considerations.

Bounded context may be consistent with the technology component. The context bounded think of the technology component does not matter. But we have to remember: You can not define technical components and bounded context. When we use the IDE's usually a bounded context is a project.

Guess you like

Origin www.cnblogs.com/zzjimmy/p/10955168.html