- Mastering Microservices with Java
- Sourabh Sharma
- 346字
- 2021-07-02 13:03:37
Bounded context
When you have different sub-models, it is difficult to maintain the code when all sub-models are combined. You need to have a small model that can be assigned to a single team. You might need to collect the related elements and group them. Context keeps and maintains the meaning of the domain term defined for its respective sub-model by applying this set of conditions. Domain models are divided into sub-models, and bounded context distinguishes the context of one sub-domain from the context of another sub-domain.
These domain terms define the scope of the model that creates the boundaries of the context.
Bounded context seems very similar to the module that you learned about in the previous section. In fact, the module is part of the bounded context that defines the logical frame where a sub-model takes place and is developed, whereas the module organizes the elements of the domain model, and is visible in the design document and the code. This also helps to isolate the models and the language from one model to another to avoid ambiguity.
Now, as a designer, you need to keep each sub-model well-defined and consistent. In this way, you can refactor each model independently without affecting the other sub-models. This gives the software designer the flexibility to refine and improve it at any point in time.
Now, let's examine the table reservation example we've been using. When you started designing the system, you would have seen that the guest would visit the application, and would request a table reservation at a selected restaurant, date, and time. Then, there is the backend system that informs the restaurant about the booking information, and similarly, the restaurant would keep their system updated with regard to table bookings, given that tables can also be booked by the restaurant themselves. So, when you look at the system's finer points, you can see two domain models:
- The online table-reservation system
- The offline restaurant-management system
Both have their own bounded context and you need to make sure that the interface between them works okay.
- Learning Cython Programming
- Rust實(shí)戰(zhàn)
- Python入門很簡(jiǎn)單
- Unity 2020 Mobile Game Development
- 從0到1:HTML+CSS快速上手
- 秒懂設(shè)計(jì)模式
- Nexus規(guī)模化Scrum框架
- Learning Hunk
- Android程序設(shè)計(jì)基礎(chǔ)
- Serverless computing in Azure with .NET
- Django 3.0入門與實(shí)踐
- Python趣味編程與精彩實(shí)例
- Mastering HTML5 Forms
- 30天學(xué)通C#項(xiàng)目案例開發(fā)
- 算法秘籍