| | - Low resource obtaining efficiency (> 1 day)
- Low resource utilization (< 30%)
| - Self-service and efficient resource obtaining (minute-level)
|
| | - Architecture coupled, a small change requires significant reconstruction
- Single technology, one technology is required to resolve all problems
- System release at a large granularity, requiring long response period
| - Architecture decoupled
Open API-based development makes the development, test, document, collaboration, and control activities of microservices are standardized and automated.
- Flexible access of various technologies
Supports Java, PHP, Python, and Node.js. The high-performance REST/RPC microservice development framework provides out-of-the-box tools to reduce the development threshold.
- Agile
The one-stop microservice governance console provides governance capabilities for microservices, such as load balancing, rate limiting, degradation, circuit breaker, fault tolerance, and fault injection. Supports microservice upgrade dark launch.
|
Installation and deployment | - Siloed system
- Manual deployment
| Developers only need to use ServiceStage and source code software repository to implement one-click automatic deployment and update. |
| | - Patch installation
- Manual upgrade
- Services interrupted
| During rolling upgrades, services are evenly distributed to new and old instances; therefore, services are not interrupted. Dark launch allows you to select users to test your beta versions, reducing launch risks and ensuring smooth rollout of new features. |
| | - Application breakdown or crash
- Slow service response
- Insufficient system resources
- Difficult fault locating
| - Real-time graphical display of application monitoring metrics
CPU usage, alarms, node exceptions, running logs, and key events can be monitored in real time
- Microservice governance
Supports microservice API-level SLA metrics (throughput, latency, and success rate) monitoring and governance in real time (in seconds), ensuring continuous service running.
|