Loopback-next: Facilitate communication between multiple (polyglot) microservices

Created on 26 Apr 2017  路  3Comments  路  Source: strongloop/loopback-next

when developing microservices it's better to have complete disconnect from even code/repo structure. Let's say we've three microservices they should be able to develop independently on their own repo and be able to deploy on their own container. The communication between two different services should be pure API. grpc has done some neat constructs around this. Can we get support for service-to-service high performant rpc style communication? Currently the only communication supported is REST, which IMO is not efficient.

feature help wanted

Most helpful comment

Check this out - https://github.com/strongloop/loopback-example-polyglot. We already have a grpc connector for LoopBack.

All 3 comments

Check this out - https://github.com/strongloop/loopback-example-polyglot. We already have a grpc connector for LoopBack.

I am closing this issue because we are not going to have time to work on this in the next 6-9 months. However, we are happy to accept a pull request contributing this feature.

Was this page helpful?
0 / 5 - 0 ratings