Switching a microservices registry from a self-managed cluster to Microservices Engine (MSE) requires careful coordination. If clients connect to the new registry before all services have re-registered, they lose visibility into the services still on the old cluster. MSE Sync solves this by synchronizing data between the source and target clusters in real time, keeping services discoverable from both clusters throughout the migration.
MSE Sync supports the following self-managed registries as migration sources:
Nacos
ZooKeeper
Eureka
Consul
Migration scope
A microservices registry manages two types of data, each with a different migration path:
| Data type | Description | Migration method |
|---|---|---|
| Service registrations | Records of running service instances, recreated each time an instance starts. | MSE Sync synchronizes service registrations between clusters in real time. |
| Configuration data | Persistent key-value pairs, namespace metadata, and other stored settings. | MSE Sync supports configuration synchronization. For Nacos, use the built-in configuration export and import feature instead (see note below). |
MSE Sync does not support Nacos configuration migration. To migrate Nacos configurations, export them from your self-managed Nacos instance and import them into the MSE Nacos instance.
Step 1: Evaluate specifications
MSE provides a built-in evaluation tool that recommends an instance size based on your current infrastructure. Use this tool before purchasing an MSE instance.
Log on to the MSE console and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Migration to Cloud.
On the Migration To Cloud page, click Specification Evaluation.
Configure the evaluation parameters:
Assess By Self-managed Instance -- Provide the vCPU count and memory size in the Self-managed Instance Node Specifications section, and the node count in the Number Of Self-built Instance Nodes section. Best when you know your current cluster hardware.
Evaluated By Application Scale -- Enter the number of pods in your Container Service for Kubernetes (ACK) cluster, or the number of processes on your Elastic Compute Service (ECS) instances, in the Number Of Application Instance Nodes section. Best when you want to size the target based on application scale.
Parameter Description Source Instance Type The registry type to migrate from: Nacos or ZooKeeper. Evaluation Method Choose one of the following methods: Click Specification Evaluation. The panel displays recommended MSE instance specifications.
Click the Purchase MSE Instance link to open the purchase page. Configure VPC and network settings, then click Buy Now.
Step 2: Configure and start the migration
After the MSE instance is ready, set up the synchronization task through a three-step wizard.
Log on to the MSE console and select a region in the top navigation bar.
In the left-side navigation pane, choose Microservices Registry > Migration to Cloud.
On the Migration To Cloud page, click Migration Configuration.
In the Deployment Tools step, follow the on-screen instructions to deploy the MSE Sync migration tool in your environment. After deployment completes, click Next.
In the Create Configuration step, configure the synchronization task:
Parameter Description Source Instance Type The registry type of your self-managed cluster: Nacos, Eureka, ZooKeeper, or Consul. Synchronization Type The scope of data to synchronize. Options: Full synchronization (both services and configurations), Configuration synchronization (configurations only), or Service synchronization (service registrations only). Source Instance Node Address The IP address and port of each source node, one per line. Format: <ip-address>:<port>(for example,192.168.100.101:2181). If the source cluster uses SLB, enter the SLB IP address and port instead.Source Instance Name (Optional) A descriptive name for the source instance. Namespaces Required for Nacos sources. Enter the namespaces to migrate, separated by commas. Leave this field blank to migrate all namespaces. Destination Instance The MSE instance to migrate to. Select from the dropdown list. Description (Optional) A description of the migration task. Click Next.
In the Implement Migration step, follow the on-screen instructions to start and monitor the synchronization process.