Microservice Application Management

Service Scenarios

Usage Scenario

In a traditional single architecture, different service models need a unified technical solution and technical platform. Each service module cannot be reused, so any faulty module will cause the entire system to become unavailable. With the increasing complexity of enterprise services, the traditional monolithic architecture becomes more and more cumbersome and inflexible. Microservice applications solve these problems.

Benefits

Microservice-based applications divide a system into several small service components. Such components communicate with each other through lightweight protocols and decouple their lifecycle management.

Ever-growing services may encounter unexpected situations such as instantaneous and large-scale concurrent access, service errors, and intrusion. The microservice architecture fine-tunes service management and control to support service requirements.

CAE manages the full lifecycle of serverless applications. Compatible runtime environments include Java, PHP, Node.js, Docker, and Tomcat, and microservice applications such as Apache ServiceComb, Spring Cloud, and Dubbo are managed without intrusion. In addition, CAE improves cloud migration with configuration management, monitoring and O&M, and service governance.

Advantage

CAE microservice application solution:

Supports multiple microservice frameworks, such as ServiceComb, Spring Cloud, Dubbo, and Service Mesh, and can be directly hosted on the cloud without changing service code.
Supports multiple languages, such as Java, Node.js, PHP, and Python.
Provides functions such as service center, configuration center, dashboard, and dark launch.
Provides complete microservice governance policies, including fault tolerance, rate limiting, service degradation, circuit breaker, fault injection, and blacklist/whitelists. Operations are available on the UI for different service scenarios, greatly improving the availability of service governance.