Preface

nacos Configuration management applications and distributed systems

From single architecture to micro service

1. Monomer architecture

Web Early application , Most of web Engineers package all functional modules together and put them in one web Running in the container , All function modules use the same database , meanwhile , It also provides API and UI Access to the web Module etc. .

Although it's also modular logic , But in the end, it will be packaged into a single application , This method deploys all functions in one web The system running in the container is called monomer architecture .
advantage :

• High development efficiency : The interaction between modules adopts local call , And save the interactive discussion time and development cost between microservices
• Easy to test :IDE Are designed to develop a single application , Easy to test , The complete system can be started directly locally
• Easy to deploy : The cost of operation and maintenance is small , Package directly into a complete package , Copied to the web Under the container, you can run .

shortcoming :

• The complexity is getting higher , Poor maintainability : All businesses are deployed together , More and more complicated , Pull one hair and move the whole body .
• The iteration speed of the version gradually slows down : To modify a place, you need to compile and deploy the whole application , Long startup time , Regression test takes too long .

2. Microservices

Many large companies , Solve the above problems by adopting micro Service Architecture . The idea is not to develop a large single application , Instead, its application is broken down into small , Interconnected microservices .
A microservice generally performs a specific function , Like order service , User service, etc . Every microservice is a complete application , All have their own business logic and database . Some micro services will also release API For other microservices and application clients .
such as , According to the system described above, it can be decomposed as follows :

Each business module uses independent services to complete , This microservice architecture pattern also affects the relationship between applications and databases , Unlike traditional methods, multiple business modules share a database , Microservice architecture each service has its own database .
Microservice benefits :

• Divide and rule , Single responsibility : Easy to develop , Understanding and maintenance , Facilitate the splitting and management of the team
• Telescopic : It can scale the specified service separately
• Parts are easy to modify , Easy to replace , Easy to deploy , Conducive to continuous integration and rapid iteration
• Not subject to any technology stack