Edition Differences
Function |
Specifications |
|
---|---|---|
Management scale |
Maximum number of application component instances in a region |
5,000 |
Maximum number of instances supported by a component |
200 |
|
Microservice |
Microservice engine |
The number of microservice engines that can be created depends on the engine type and the number of VMs in the AZ where the microservice engine is located. Each AZ can contain a maximum of 50 VMs. A cluster-deployed microservice engine consumes five VMs. |
Java microservice development SDK |
Supported |
|
Spring Cloud microservice access |
||
Registry center |
||
Configuration center |
||
Real-time dashboard |
||
Load balancing |
||
Rate limiting |
||
Service degradation |
||
Fault tolerance |
||
Circuit breaker |
||
Fault injection |
||
Blacklist and whitelist |
||
Application lifecycle management |
Multi-language application management (Java, PHP, Python, Node.js, Tomcat, and Docker) |
Supported |
Application lifecycle management (auto scaling, upgrade, rollback, start, stop, restart, and deletion) |
||
Basic application monitoring (running status, CPU, memory, and disk usage) |
||
Container-based deployment. Java, PHP, Python, Node.js, Tomcat, and Docker are supported. |
||
Access control |
||
Application domain name management |
||
Auto scaling |
||
Event analysis |
||
Log analysis |
||
Threshold rules |
||
Deployment source management |
Docker image package management |
Supported |
Repository permission management |
||
Application operations management |
Log storage and search |
1 TB/month; storage duration: 30 days |
Log analysis |
500 GB |
|
API call (log data query) |
10 GB/month |
|
Host monitoring |
200 VMs; storage duration: 1 year |
|
Metrics in real-time monitoring |
2000 |
|
Custom metrics |
500 |
|
API call (metrics query) |
5,000,000 times/month |
|
Events and alarms |
500,000 records/moth; storage duration: 30 days |
|
Intelligent threshold rules |
50 |
CSE Instance Specifications
Microservice engines have professional and exclusive editions.
- Professional microservice engine: Cloud Service Engine (CSE) is a free experience engine provided by ServiceStage. You can use a professional engine to experience all product capabilities of ServiceStage, such as service governance and configuration management. Engines are shared by all tenants; however, the performance may be affected by other tenants. A professional engine cannot be upgraded to the exclusive edition.
- Exclusive microservice engine: Exclusive engines are commercial engines that manage large-scale microservice applications. You can select different engine specifications based on service requirements, and specifications cannot be changed. Exclusive engines are exclusively used; therefore, the performance is not affected by tenants.
The following describes the maximum number of instances supported by CSE.
Type |
Microservice Instances |
Configuration Items |
---|---|---|
Professional microservice engine |
1,000 |
- |
Exclusive microservice engine |
100 |
600 |
500 |
3,000 |
|
2,000 |
12,000 |
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