Three system architecture follows the principle of
improving the user experience: to enhance the user experience, reduce churn
improve agility: timely response to business needs, and promote the development of enterprises
to reduce costs: reduced costs of products, customers or business plan of
the traditional architecture of the monomer
first look see traditional single project chart
It concluded from FIG single application architecture:
Traditional single application architecture feature set, code and data center technology, a package after the release of the deployment running in the same process application.
High complexity: Because it is a single archive file, the module that contains the project file is very large, leading module boundaries blur, dependence is not clear, code quality is uneven, chaotic heap together, making the whole project is very complicated. So that every time you modify the code, very careful, could add a simple function, or modify a Bug will bring hidden defects.
Technical debt: Over time, changes and replacement demand for technical personnel, technical debt will gradually form application, and piled up.
Limited expansion capability: single application can only be extended as a whole, can not be scaled as needed business modules.
Micro Services Architecture
Let's look at the micro-service architecture diagram
The following conclusions from the micro-service architecture diagram:
Micro-service responsibilities to each single function in a stand-alone service.
Each service has multiple instances running, each instance can be run in a platform within the container, the stretch effect for smooth, rapid single micro service starts.
Each service should have its own operating platform, as well as exclusive operations personnel, including technical operation and maintenance and operations personnel: Each service high degree of autonomy, changes within the external transparent.
Easy to develop and maintain: a micro service will focus on a specific business function, so the business is clear, smaller amount of code. Development and maintenance of a single micro service is relatively simple.
Partial modification easy to deploy: application as long as the modified monomers, have to re-deploy the entire application. Micro service solves this problem. In general, a micro-service modify only need to re-deploy the service.
Unlimited technology stack: micro-services architecture can be combined with the characteristics of the project team and business, a reasonable choice of technology stack.