EDITORIAL
For areas of business, business models, solutions, BC, domain model, micro-services these concepts are often hard to tell, but the knowledge domain modeling and DDD during the process of landing and more important.
Areas of business and business model
- Areas: the problem domain, the problem space, the field is a boundary, range, an area often represent a problem domain boundary, the larger the business, the greater the area of the border.
- Establish boundaries around areas of business, because the different business, so there is also the size of the field and the field is divided, carved out of the field become subdomains, each subdomain corresponds to a small problem or a small business, but also because of the importance of the different domains and sub-divided into core support subdomains.
- Business often corresponds to a business model, starting from the business itself, to analyze the relationship between the various business scenarios within the boundaries of business, and business concepts. Get the business model most commonly used method is a noun verb adjective analysis, as well as four-color prototype of such analysis, to find a suitable, business model and refining the concept of core business relationships, it can help us better understand the business itself.
solution
When DDD practice, back needs analysis, field division, modeling and other areas of work, the floor system needed a solution, if achieved a business platform, requires a complex system solutions, if the design is too large, modules, components with soft, is not conducive to the maintenance of the entire system - Evolution - stretching and other needs. So it is necessary to split the solution, become a small independent solutions.
Field represents the problem domain, solutions represent the solution space
Split the solution often is no shortcut, or need experience, familiarity with the situation of the system and so on. Use a variety of software design principles, best practices, design patterns, non-functional characteristics of the demand, and the situation to guide the team to split and fall of our solutions.
Split sometimes cut from a performance point of view, can sometimes be cut from a business point of view, can sometimes help CQRS, or flexible point of view, to find their own situation for their own teams and projects, the most suitable is the best.
BC
BC as a boundary context, is the core concept of DDD, and there are two concepts Bounded Context, a scene entangled various contexts, the concept of a sense of time and space. Can the domain model objects within the boundaries of the concept of the context boundary clearly, if there is no border this context, there is ambiguity same concept could produce deviations understand. BC commodity goods, such as the center is the root of the polymerization, in order BC different meanings, but a value object.
Domain Model
Domain model is the core concept of DDD, is a business split, the combined result of software design, any domain model are meaningful within a specific BC border.
Business model is to express the concept of business and their relationship, the domain model the business model based on the use thought OOA / D for further abstract design model, field model with a polymeric entity, identifies the value of the object. Multiple business models can hybridity into a domain model.
Domain modeling process performed substantially:
- Get the business model
- Apply principles of software design and business model refinement model
Micro Services
After the emergence of micro-services for micro-services division in BC and DDD have a great meeting point with the same principle to explore the boundary.
to sum up
- Field of the problem domain = = = business problem space boundary
- The question every business can derive a business model
- Field splitting, business modeling, is needs analysis phase needs to be done
- Split, domain modeling solutions, software design stage to do things
- BC is the solution to the border
- BC border boundary fit micro services
Reproduced in: https: //my.oschina.net/u/1000241/blog/3059215