Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
Show all
Copied.
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.
- Implements mutual discovery between Spring Cloud, ServiceComb, and Java chassis.
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