Definition of Microservice:
It is a design style in the system architecture. The main purpose is to split an originally independent system into multiple small services. These small services run in their own independent processes, and the services communicate and cooperate through the Http-based Restful API. . Each small service that is split is built around a certain item or some highly coupled business
functions in the system, and each service maintains its own data storage, business development, automated test cases and independent
deployment mechanism. These microservices can be written in different languages thanks to a lightweight communication and collaboration base.
Differences from monolithic systems:
In the traditional enterprise system architecture in the past, we usually use objects or business types to build a single project for a complex business requirement. In the project, we usually divide the requirements into three main parts: database, server-side processing, and front-end presentation. In the early stage of the business, since all business logic is in one application, development, testing, and deployment are relatively simple. However, with the development of the enterprise, the system will continue to add different business modules to the single project in order to meet different business needs. At the same time, with the advancement of mobile devices, the front-end display module is not limited to the form of the web. More interface modules are required for system back-end to front-end support. Monolithic applications face a wider range of business requirements, and the ever-expanding demands will make monolithic applications larger and larger, and the problems of monolithic applications will become prominent. Since a single system is deployed in a process, we often modify a small function, which will affect the operation of other functions in order to deploy and go online. Maintenance costs are too high to control.
Modules are split, and services are deployed and expanded independently. Since each service runs in its own process, there is a stable boundary in deployment, so that the finer details of each service will not affect the operation of other services. Because it is deployed independently, we can more accurately evaluate the performance capacity of each service. By cooperating with the cooperation process between services, we can more easily find the bottleneck position of the system, and give a more accurate system-level performance capacity evaluation.