What Are the Differences Between the Microservice and Common Application?

Development

The workload of a microservice is light. A two-pizza team can rewrite all the code of a microservice in two weeks. This can be used as a symbol of microservices. When developing a microservice, its APIs need to be available for interconnection with other microservices. Therefore, the API definition-based development mode is highly recommended.

For details about microservice development, see Developing Microservice Applications.

Complex logic, coupled modules, bloated code, difficult modification, and low version iteration efficiency.

Deployment

An application consisting of multiple microservices is complex. Orchestration is required when the application is deployed.

For details about microservice application deployment, see Creating and Deploying a Component.

Applications are probably large and require much time to build and deploy. This is not conducive to frequent deployment and hinders continuous delivery. This problem is especially serious in mobile application development.

O&M

Microservice O&M focuses on governance, in addition to metrics monitoring and log collection. The core concept of microservice governance is to maintain system performance through modifications while the system is running.

For details about application O&M, see Component O&M.

It takes a long time to rectify common online problems. To rectify any online problem, the entire application system must be upgraded.