Documentation: Creating and communicating with microservices.

[mschnee]

User Story

There are multiple ways to set up microservices:

• Have a public facing API Gateway responsible for authentication, that then acts as a proxy for internal microservices, or which can have orchestration logic on top of their responses.
• Have many public facing services- one responsible for the process of authentication and the frontends are responsible for knowing.

There are also multiple ways to perform communication:

• Loopback 4 supports creating an OpenAPI JSON based datasource when using lb4 service.
• HTTP REST
• rpc, gRPC, redis/socket notifications.

There are different ways to organize the source code:

• A monorepository, using something like lerna to manage versioning and publishing.
• Separate repositories managed by different teams.

It would be great to have documentation and examples that could cover these cases. Example:

• Creating a loopback4 microservice as a REST Server that can expose an openapi.json file, and a loopback4 api gateway responsible for authentication and consuming those microservices.
• Creating a loopback4 microservice as a gRPC server that can publish proto files (to a private repository, or just on github for consumption), and a loopback4 api gateway responsible for authenticating and consuming those microservices.
• Workflows for maintaining multiple services with minimal manual code intervention.

[BillyCottrell]

Hi, any updates on this?

I am trying to implement the microservice architecture and I would like to know how to build it using Loopback 4 except that there is no documentation or examples on how to create microservices and gateways. It could be interesting perhaps to have information on using a registry to automatically register new instances of a microservice so things like load balancing could be used.

Thanks in advance!