How to add a downstream grpc support while keeping upstream normal HTTP?

[simboyd]

Hi, I'd like to receive HTTPS requests from the client in my Ocelot gateway API and call existing grpc microservices to aggregate data and return it back to the client over HTTPS in JSON format. sorry if this is a silly question but how would I go about implementing a mechanism for translating HTTP requests into grpc messages downstream? Where do I begin?

[ks1990cn]

No you can not, it due to different protocols, GRPC have concurrency limit, you need different type of Load balancers. Probably need to write logic for socket so continuously it will be alive.
GRPC is made for high performance and you may loose that.
Try using it as per recommendations, please go for Rest API if you need highly scalled and highly perfomant system with JSON result back.

• Performance best practices with gRPC

[raman-m]

True concerning performance, but the author wants to integrate 😄

[raman-m]

@simboyd on Nov 25, 2022

Hello, Sandro!
Welcome to Ocelot world!
Sorry, we've missed the thing for a year...
Are you still with Ocelot?

---

how would I go about implementing a mechanism for translating HTTP requests into GRPC messages downstream?

In theory it is possible. But that will be your custom solution, you see?

---

Where do I begin?

As a known fact, Ocelot does not support GRPC protocol & scheme now. We plan to discuss GRPC in 2-3 months (in 2024). Good point to create a milestone...

There is only one option...
You need to develop a custom Delegating Handler to convert HTTP request to GRPC one. After that you have to process GRPC response to convert it back to HTTP one. So, delegating handlers feature is a great ASP.NET Core feature which helps to override everything! 😍

That will be very interesting coding challenge! 😉
Please, create Ocelot fork in your repos... And let's get started!