This repository has been archived by the owner on Nov 7, 2020. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 23
Microservices? API Gateway? #126
Labels
Projects
Comments
Current idea is. Use HTTP, same as now, for API requests. Use Istio to handle proxying to actual services. For connection between services, instead of using now direct ts calls, we will split all modules to microservices and use gRpc to communicate between them. Pros:
Cons:
|
8 tasks
TODO Code:
TODO Pipeline:
TODO Infra:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Investigate if this would be worth the effort.
It wouldn't be as hard to implement as we we would just need to remove controllers from each module and replace it with a protocol of choice that would expose *.service.ts public methods.
This way we would have one API Gateway module, with http/websocket (could even split websocket to own gateway?), that would have http controller and just send requests to appropriate microservice.
Benefits:
1. direct client to microservice communication versus the api gateway pattern
2. microservices - apigateway
The text was updated successfully, but these errors were encountered: