+1 I'm glad to hear this. I think that the Mesher can be used as a multi-language sub-project or component, and provide a unified user interface for service registration and discovery, governance, configuration to users.So that ServiceComb can form a more diversified solution, bringing multi-optional microservice solution to users with different scenarios and requirement.
Best Wishes & Regards ------------------------------- Mabin Mohammad Asif Siddiqui <asifdxtr...@apache.org> 于2019年6月11日周二 上午9:49写道： > +1 > > I strongly suggest to add Mesher as a part of ServiceComb as it will make > ServiceComb a fully fledged microservice framework with support to all > languages by either java-chassis or by mesher. > > Regards > Asif > > On 2019/06/10 06:11:01, Xiaoliang Tian <xiaoliang.t...@gmail.com> wrote: > > 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 > > >
