Select an instance type and an instance edition - Microservices Engine

Microservices Engine (MSE) instances support the Nacos and ZooKeeper engines. MSE provides Professional Edition and Developer Edition instances. Developer Edition instances are single-node instances and are not suitable for production environments. You can select the required engine type and instance edition based on the comparison descriptions in this topic.

Select an MSE instance edition

Note

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.
We recommend that you use the MSE Nacos engine instead of the open source Eureka 2.x 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.

Nacos engine

Item	Professional Edition	Developer Edition
Supported engine versions	Nacos 2.0.x Nacos 2.1 (seamlessly compatible with Nacos 1.x clients and Nacos 2.x clients)	Nacos 2.0.x Nacos 2.1 (seamlessly compatible with Nacos 1.x clients and Nacos 2.x clients)
High availability	By default, instances are evenly deployed across zones to improve the disaster recovery capabilities of the instances. Node failures are automatically detected and fixed. A service-level agreement (SLA) of up to 99.95% is provided. Dynamic configuration and scaling without restarts are supported. The service downtime is reduced.	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.
Observability	Registry monitoring, configuration center monitoring, and resource usage monitoring are supported. Metrics and dashboards related to service pushes, the number of persistent connections, client version, and Java virtual machine (JVM) are provided.	Registry monitoring, configuration center monitoring, and resource usage monitoring are supported.
Expert service	Product experts and R&D experts provide online support to help you resolve online issues at the earliest opportunity. Suggestions on stability improvement, parameter tuning, and best practices are provided.	Not supported.
Alert management	Supported.	Supported.
Access authentication	Supported.	Supported.
Configuration encryption	Supported.	Supported.
Eureka protocol	Supported.	Supported.
Diamond protocol supported by Application Configuration Management	Supported.	Supported.
Empty list protection	Supported.	Supported.
Traffic interworking between non-Java applications and Java applications	Supported.	Supported.
Graceful migration	Supported.	Supported.
Configuration push tracking	Supported.	Not supported.

ZooKeeper engine

Note

For instances that use ZooKeeper Professional Edition, a maximum of 2,000 ephemeral nodes can be created in 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 ZooKeeper Developer Edition is upgraded to Professional Edition.

Item	Professional Edition	Developer Edition
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	By default, instances are evenly deployed across zones to improve the disaster recovery capabilities of the instances. Node failures are automatically detected and fixed. An SLA of up to 99.95% is provided. Dynamic configuration and scaling without restarts are supported. The service downtime is reduced.	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 hot reloading mechanism is optimized, the speed of class loading is improved, and the service downtime during the startup is reduced.	The instance performance is basically the same as the performance of open source instances.
Features	The number of child nodes is limited. You can create a custom policy to prevent excessive child nodes from being created and affecting the performance of an instance.	Basic features are provided.
Expert service	Product experts and R&D experts provide online support to help you resolve online issues at the earliest opportunity. Suggestions on stability improvement, parameter tuning, and best practices are provided.	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.