The deployment architecture was upgraded to the microservice architecture due to the pain points of the monolithic architecture

The figure shows a single deployment

 Pain points Multi-person collaboration may generate a lot of regression tests Code management complexity increases Software package upgrades will increase the number of tests

Example of single e-commerce 1 Add function (add mini program platform) 2 Concurrent increase

1. Code reuse 2. Mutual calls between systems 3. The interface must not only provide external services, but also provide internal interfaces

         4 The data analysis function may cause database performance problems 5 The database is dependent on multiple services and cannot be split and upgraded

         6. Each service communicates with the table as an intermediary. 7. A certain interface is not well written, which leads to serious performance problems in the database.

         8 Development and testing, difficult deployment

Code isolation (as follows) will still be the problem. If the database is not isolated, it will still affect each other.

Generate new problems completely independently Add interfaces to increase workload Increase developers Internal http protocol is inefficient

The basic structure of ordinary microservices is as follows

Hierarchical Microservice Transformation Improvement of Internal Call Efficiency

 

 A series of new problems to be solved for layered microservices Is the ip port service healthy...  

Architecture Evolution Series

Guess you like

Origin blog.csdn.net/pzl_pzl/article/details/130247872