All Products
Search
Document Center

Microservices Engine:Select an engine type and edition

Last Updated:Mar 03, 2026

Microservices Engine (MSE) supports two engine types -- Nacos and ZooKeeper -- and two editions -- Professional and Developer. Choose an engine type based on your application stack and workload, then select an edition based on your availability and support requirements.

Important

MSE does not support edition changes after instance creation. You cannot upgrade from Developer Edition to Professional Edition, or downgrade from Professional Edition to Developer Edition. To switch editions, create a new instance and migrate your workloads.

Engine types

MSE Microservices Registry provides Nacos and ZooKeeper engines for service registration, discovery, and configuration management.

  • Nacos engine: Runs Nacos 2.x by default and is compatible with earlier Nacos versions. Fully compatible with the Eureka protocol, delivering 50% better performance than open-source Eureka.

  • ZooKeeper engine: Runs ZooKeeper 3.8.0 by default and is compatible with versions from ZooKeeper 3.4.0 onward.

When to use each engine

ScenarioRecommended engineReason
Migrating from self-managed NacosNacosDirect compatibility with existing Nacos clients
Migrating from self-managed EurekaNacosFull Eureka protocol support; open-source Eureka 2.x is discontinued and Eureka 1.x receives no new features
Migrating from self-managed ZooKeeperZooKeeperDirect compatibility with existing ZooKeeper clients
New microservices deploymentNacosRich feature set for service discovery and configuration management
Big data and distributed coordinationZooKeeperBuilt-in distributed locks, distributed queues, and high availability (HA) coordination

Editions

MSE offers two editions for both engine types:

  • Professional Edition: For production workloads requiring multi-zone HA, a Service-Level Agreement (SLA) of up to 99.95%, enhanced performance, and expert support.

  • Developer Edition: For development, testing, and non-critical workloads with single-node deployment and open-source-level performance.

Features shared across both engines

The following capabilities apply to both Nacos and ZooKeeper engines, with differences between Professional Edition and Developer Edition.

FeatureProfessional EditionDeveloper Edition
Deployment modelMulti-zone: instances deployed evenly across availability zones with automatic node failure detection and recoverySingle-node: no multi-zone disaster recovery
SLAUp to 99.95%No SLA guarantee
Dynamic scalingScale and reconfigure without restarts, reducing service downtimeNot supported
Runtime optimizationBuilt on Alibaba Dragonwell with deep tuning; overall performance improved by more than 40%Open-source-level performance
Expert serviceProduct and R&D experts provide online support, stability recommendations, parameter tuning, and best practicesNot supported
Alert managementSupportedSupported
Graceful migrationSupportedSupported
Graceful migration allows you to migrate Spring Cloud and Dubbo applications from a self-managed registry to MSE without modifying code or suspending services. Application access is unaffected during migration.

Nacos-specific features

FeatureProfessional EditionDeveloper Edition
Supported engine versionsNacos 2.0.x, Nacos 2.1 (compatible with Nacos 1.x and 2.x clients)Nacos 2.0.x, Nacos 2.1 (compatible with Nacos 1.x and 2.x clients)
ObservabilityRegistry, configuration center, and resource monitoring. Advanced metrics and dashboards: service pushes, persistent connections, client version, Java Virtual Machine (JVM).Registry, configuration center, and resource monitoring
Access authenticationSupportedSupported
Configuration encryption (via Key Management Service (KMS))SupportedSupported
Eureka protocolSupportedSupported
Diamond protocol (Application Configuration Management)SupportedSupported
Non-Java and Java application traffic interworkingSupportedSupported
Empty list protectionSupportedSupported
Configuration push tracksSupportedNot supported

Feature descriptions:

  • Access authentication: Prevents unauthorized users from accessing Nacos instances. Keeps configurations confidential and secure.

  • Configuration encryption: Encrypts configurations using Key Management Service (KMS). Ensures encrypted storage and transmission.

  • Traffic interworking (non-Java and Java): Enables communication between applications deployed on Alibaba Cloud Service Mesh (ASM) instances and Java applications registered with MSE, based on service discovery.

ZooKeeper-specific features

Important

For ZooKeeper Professional Edition instances, a maximum of 2,000 ephemeral nodes can be created per session to maintain instance stability. Review the ephemeral node configuration on your client and evaluate whether throttling affects your workloads before migrating from Developer Edition.

FeatureProfessional EditionDeveloper Edition
Supported engine versionsZooKeeper 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)
Hot reloading optimizationOptimized class loading and reduced startup downtimeNot optimized
Child node managementCustom policies to limit child node count and prevent performance degradationBasic features only

Recommended edition by use case

Use caseRecommended editionKey reasons
Production services with end usersProfessional Edition99.95% SLA, multi-zone HA, automatic failure recovery
Applications requiring expert guidanceProfessional EditionAccess to product and R&D experts for stability and tuning
High-throughput workloadsProfessional Edition40%+ performance improvement via Alibaba Dragonwell optimization
Development and testingDeveloper EditionCost-effective single-node deployment for non-critical environments
Proof-of-concept projectsDeveloper EditionSufficient for validating application architecture
Non-critical internal toolsDeveloper EditionBasic feature set meets non-production requirements

References