Replies: 1 comment
-
What is your routing criteria? gRPC starts as HTTP, so long as you're routing based on the initial request (path, headers, etc.) you don't need to do anything special. It only gets hard if you want to route based on the body. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I want to develop a server with an API gateway that receives gRPC requests and routes them to the right service
( the sub service is also gRPC ) -
The examples I've found only show using an aggregator where the gateway receives RESTful requests and routes them to an aggregator that creates the proto and calls the right gRPC service.
I want to do this without an aggregator - has anyone tried building a gRPC API gateway that directly routes gRPC requests to the appropriate backend services?
How would I implement this?
Beta Was this translation helpful? Give feedback.
All reactions