官术网_书友最值得收藏!

Context boundaries

A module is just a way of defining a context boundary. If you want to migrate your existing monolithic application to a microservice-based application, you first have to identify a hidden context within your current application. This means we have to define the context and draw explicit context boundaries. This helps us design a robust microservice-based application.

For example, a typical online book shopping portal can have an order and shipping module using the same entity product. The following diagram shows the context boundaries of this application:

As you can see in the preceding diagram, the distributed application is based on different bounded contexts. The preceding design is a modular application design, where every module runs an independent process as a service. This is a decentralized approach to application design.

Once you have defined context boundaries, you can then easily decompose your existing monolithic application into a microservice-based application, where each bounded context has one microservice. In the example shown in the previous diagram, we have divided our monolithic application into four bounded contexts, which means that there are four microservices: Order Service, Book Service, Shipping Service, and Customer Service.

We now have a separate product entity in the Order Service and the Shipping Service, which each have their respective repositories. This concept can be extended by defining explicit context boundaries for the Stock and Inventory modules and creating an independent microservice for each.

Let's have a look at two different decomposition approaches. A monolithic application can be decomposed based on either its business capability or its domain.

主站蜘蛛池模板: 额尔古纳市| 柏乡县| 太仆寺旗| 阿图什市| 宾川县| 蒙城县| 图木舒克市| 博乐市| 宁都县| 永胜县| 浦城县| 聂拉木县| 永仁县| 阜康市| 云浮市| 琼结县| 印江| 福建省| 阿勒泰市| 师宗县| 景宁| 团风县| 泸溪县| 凤阳县| 航空| 五台县| 竹北市| 桐柏县| 衢州市| 宕昌县| 平度市| 武陟县| 综艺| 全南县| 喀什市| 调兵山市| 庆元县| 公安县| 渝北区| 台中市| 湄潭县|