当前位置:网站首页>Splitting e-commerce system into micro service

Splitting e-commerce system into micro service

2022-01-15 02:08:45 InfoQ



1、 Service split

  • Conclusion
As shown in the system architecture diagram , The business layer is mainly divided into 10 Domains ,8 A service ( Fields of the same color are placed in the same microservice ).
  • Resolution principle
  There are mature cases in the e-commerce system industry , Therefore, refer to the industry to realize ,
Split by business
, And because the front end does not need to participate in the development of all domains , Therefore, it is mainly based on the number of back-end developers , follow
Three Musketeer principles
(25/3=8), Split into 8 Micro services ( For one more ).
  • Implementation details
Allocate personnel with different abilities according to the importance and complexity of each service business . For example, commodities 、 Order 、 stock 、 Payment is the most important part of e-commerce system , And the workload of these modules is large in the initial stage , Capable personnel can be assigned ; The store 、 In the initial stage of after-sales modules, only basic capabilities need to be established , Gradually improve in the later stage , Personnel with relatively weak ability can be assigned .

2、 Infrastructure selection

  • Conclusion
As shown in the system architecture diagram , Infrastructure includes : The remote invocation (Dubbo)、 Distributed database (Mysql)、 Distributed cache (Redis)、 Distributed message (RocketMQ)、 Configuration center 、 Real time monitoring, etc ;
  • Microservice framework option reason
Microservice framework selection Dubbo The reason is : The team's back-end developers are java, Can choose
The embedded SDK Pattern
,Apache Dubbo  It's a high performance 、 Lightweight open source
 Java 
Service Framework .

版权声明
本文为[InfoQ]所创,转载请带上原文链接,感谢
https://chowdera.com/2021/12/202112122239197609.html

随机推荐