rottenmu / nacos-sync

Synchronization component

NacosSync

Function

• Console: provide API and console for management
• Worker: provider the service registration synchronization.

Architecture

Architecture Topology

            +-------------+
     +----> |NacosClusterA|
     |      +-------------+               +-------------+
     |                                    |NacosClusterB|
Pull |                                    +--+----------+
Info |      +------------+                   ^
     |      |ZooKeeper   |                   |
     |      +--+---------+                   | Push Info
     |         ^ Pull Info                   |
     |         |                             |
     |        ++-----------------------------+--+
     <--------+  NacosSync1, NacosSync2,....    |
              +---+-------------------------+---+
                  |                         |
                  |                         |
                  |                         |
                  |       +---------+       |
                  +-----> |NacosSync| <-----+
                          |Database |
                          +---------+

Architecture HighLights

• All registration information will be stored in NacosSync DB.
• Multiple NacosSync instances will perform the same job.
  • Multiple NacosSync instances ensure high availability.
  • Multiple NacosSync instances performing the same job ensure the simplicity.
  • NacosCluster target will dedup the synchronization information from Nacos.

Quick Start:

• Swagger API: http://127.0.0.1:8081/swagger-ui.html#/
• Web Console: http://127.0.0.1:8081/
• Others: TBD

NacosSync Migration User Guide

Manual Goal

• Start the NacosSync service
• Use a simple example to demonstrate how to migrate a Dubbo client registered in the Zookeeper Registry to the Nacos Registry

Prerequisites

Before you begin, install the following:

• 64bit OS: Linux/Unix/Mac/Windows supported, Linux/Unix/Mac recommended.
• 64bit JDK 1.8+: downloads, JAVA_HOME settings.
• Maven 3.2.x+: downloads, settings.
• MySql 5.6.+

Download & Build From Release

There are two ways to get NacosSync.

• Download run package
• Download source code from Github

cd nacosSync/
mvn clean package -U

The path to the target file:

nacos-sync/nacossync-distribution/target/nacosSync.0.3.0.zip

After extracting the installation package, the directory structure:

nacosSync
├── LICENSE
├── NOTICE
├── bin
│   ├── nacosSync.sql
│   ├── shutdown.sh
│   └── startup.sh
├── conf
│   ├── application.properties
│   └── logback-spring.xml
├── logs
└── nacosSync-server.jar

Initialize The DB

The default is Mysql database, which can support other relational databases

• Build db schema, the default schema name nacos_Sync.
• Tables do not need to be created separately, which is conducive to hibernate's automatic table creation function.
• If the automatic table creation fails, you can build the table nacosSync.sql, the table statement is in the bin folder.

DB Configuration

In the bin folder, application.properties:

spring.datasource.url=jdbc:mysql://127.0.0.1:3306/nacos_sync?characterEncoding=utf8
spring.datasource.username=root
spring.datasource.password=root

Start Server

$ nacosSync/bin:
sh startup.sh  start

Admin Console

http://127.0.0.1:8081/#/serviceSync