[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhinan Lin resolved SCB-1295. ----------------------------- Resolution: Fixed > Syncer for synchronize data between multiple service centers > ------------------------------------------------------------ > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center > Affects Versions: service-center-1.3.0 > Reporter: Zhinan Lin > Assignee: Zhinan Lin > Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > Time Spent: 10m > Remaining Estimate: 0h > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)