Microservices Engine (MSE) instances support the Nacos and ZooKeeper engines and provide the Professional Edition and Developer Edition for the engines. Developer Edition instances are single-node instances and are not suitable for production environments. You can select the required engine type and engine version based on the comparison between the engines.
MSE instances do not allow you to upgrade an engine from the Developer Edition to the Professional Edition or downgrade an engine from the Professional Edition to the Developer Edition.
The Basic Edition is discontinued for MSE instances. For more information about the features of the Basic Edition, see Select an edition.
We recommend that you use the MSE Nacos engine because open source Eureka 2.x is discontinued and no new features are released for open source Eureka 1.x. The MSE Nacos engine is fully compatible with the Eureka protocol and delivers 50% better performance. For more information about how to create a Nacos engine, see Create a Nacos engine.
Engine type | Item | Professional Edition | Developer Edition |
Nacos | Supported engine versions |
|
|
High availability |
| Single-node deployments are used. Multi-node disaster recovery capabilities cannot be provided, and your SLA objective may not be achieved. | |
Performance | Instances are developed based on Alibaba Dragonwell and are deeply tuned. The overall performance is improved by more than 40%. | The instance performance is basically the same as the performance of open source instances. | |
Expert service |
| Not supported. | |
Access authentication | Supported. | Supported. | |
Configuration encryption | Supported. | Supported. | |
Eureka protocol | Supported. | Supported. | |
Diamond protocol supported by Application Configuration Management | Supported. | Supported. | |
Traffic interworking between non-Java applications and Java applications | Supported. | Supported. | |
Graceful migration | Supported. | Supported. | |
Push tracks of services and configurations | Supported. | Not supported. | |
ZooKeeper | Note For instances that use ZooKeeper Professional Edition, a maximum of 2,000 ephemeral nodes can be created for a single session. This ensures the stability of ZooKeeper instances. View the configuration of ephemeral nodes of your instance on the client and check whether your business is adversely affected due to throttling after the version upgrade. | ||
Supported engine versions | ZooKeeper 3.8.0 (compatible with versions 3.4.x to 3.8.x) | ZooKeeper 3.8.0 (compatible with versions 3.4.x to 3.8.x) | |
High availability |
| Single-node deployments are used. Multi-node disaster recovery capabilities cannot be provided, and your SLA objective may not be achieved. | |
Performance |
| The instance performance is basically the same as the performance of open source instances. | |
Observability | The data of more than 70 metrics is displayed. A variety of default key monitoring and alerting metrics are added. | The data of basic metrics is displayed. | |
Features | The number of child nodes is limited. You can create a custom policy to reduce the impact of excessive child nodes on the read and write performance of an instance. | Basic features are provided. | |
Expert service |
| Not supported. | |
Graceful migration | Supported. | Supported. | |
Item description:
Access authentication: This feature prevents unauthorized users from accessing Nacos instances and keeps configurations confidential and secure.
Configuration encryption: This feature allows you to encrypt configurations by using Key Management Service (KMS) and ensures encrypted storage and transmission of configurations.
Traffic interworking between non-Java applications and Java applications: This feature enables traffic interworking between applications deployed on Alibaba Cloud Service Mesh (ASM) instances and Java applications that are registered with MSE instances based on service discovery.
Graceful migration: This feature allows you to migrate Spring Cloud applications and Dubbo applications from a self-managed registry to an MSE instance in the cloud without the need to modify code or suspend services. Access to the applications is not affected during the migration process.