+1 Motivation is strong... we need to bridge this gap for Servicecomb community
-----Original Message----- From: bismy [mailto:[email protected]] Sent: Thursday, June 16, 2022 2:54 AM To: dev <[email protected]> Subject: 回复：[Discussion] Create a new project servicecomb-service-center-istio +1 Sounds a good idea. ------------------ 原始邮件 ------------------ 发件人: "dev" <[email protected]>; 发送时间: 2022年6月16日(星期四) 中午11:06 收件人: "dev"<[email protected]>; 主题: [Discussion] Create a new project servicecomb-service-center-istio Hello all, I suggest creating a new project servicecomb-service-center-istio to integrate servicecomb-service-center with istio, I will briefly introduce why we are doing this project. *1. What is servicecomb-service-center-istio?* - It's a tool that synchronizes servicecomb-service-center microservice registration information to Istio. - It enables the Istio service to discover microservices registered to servicecomb-service-center. *2. Motivation?* - Application Modernization customers who are migrating Microservices from the traditional Registry (servicecomb-service-center) to the Service Mesh (istio) have a high demand for this tool to break the communication barrier between two heterogeneous tech stacks which is caused by the different Registration and Discovery mechanisms. - Other communities (Nacos <https: github.com="" alibaba="" nacos="" tree="" develop="" istio=""> and consul <https: github.com="" aeraki-mesh="" consul2istio="">) already have this capability. Any ideas? Regards, Shiqi</https:></https:></[email protected]></[email protected]>
