How Are Microservice and Common Applications Different?
Microservice architecture breaks an application into multiple parts. Therefore, microservice applications are actually distributed applications.
Such applications are more responsive and reliable.
Type |
Microservice |
Common Application |
---|---|---|
Development |
Light workloads. A two-pizza team can rewrite all code in two weeks. 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. |
Heavy workloads. Complex logic, coupled modules, bloated code, difficult modification, and low version iteration efficiency. |
Deployment |
Multiple-microservice complexity requires orchestration. For details about microservice application deployment, see Creating and Deploying a Component. |
Large size requires long build and deploy times. This is not conducive to frequent deployment and hinders continuous delivery. This affects mobile apps the most. |
O&M |
Focuses on governance (in addition to metrics monitoring and log collection). The core concept is about maintaining system performance through modifications while the system is running. For details about application O&M, see Component O&M. |
Focuses on full upgrading to rectify online faults. This concept takes a long time. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot