Hi, this seems a good idea. But this is a big topic, I just have following questions to discuss with
1. What's the relationship between mesher and istio? As I know, istio is an excellent framework for service discovery and governance, and is very extensible. Can mesher work with istio or act as part of it? 2. Will mesher make some gread features like SWAGGER base API metadata registration? This metadata can be used for discovery and governance, which is quite like servicecomb did. 3. Does mesher have plan to change the configurations to accommandate to servicecomb-java-chassis configurations style, to make them work like a whole? -----邮件原件----- 发件人: Xiaoliang Tian [mailto:xiaoliang.t...@gmail.com] 发送时间: 2019年6月10日 14:11 收件人: dev@servicecomb.apache.org 主题: [PROPOSAL]a new project mesher for servicecomb Hi All, Service mesh is a solution for microservice, mesher is a service mesh implementation. if servicecomb introduce mesher, it will get some benifits. 1. user of servicecomb can choose any language and leverage same service center and govenance policy. 2. user can gain better performance by using java chassis and mesher, than user use service mesh solution only. the first one is most important reason why service mesh is important to service comb The mesher feature has been finished [1] there is the list of features: 1. service discovery, load balancing, circuit breaker, rate limiting, most of features that java chassis has 2. An admin API to expose runtime imformation of mesher 3. support grpc and http1 and http2 4. support transparent TLS communication 5. run as a sidecar proxy for a service 6. a sidecar injector to automattically inject mesher into k8s pod [1] https://github.com/go-mesh/mesher Regards
