But what if we could make some changes to enable clients to interact with our gRPC API as though it were a REST service? Our service won't be RESTful since it will still be RPC under the covers, but we will get to access it via HTTP/1.1, URLs, and JSON. Thankfully, we can use an Envoy proxy server to easily accomplish this feat without having to write our own code manually! - Source: dev.to / about 2 years ago
Have a look at Envoy (https://envoyproxy.io) and the Postgres filter (https://www.envoyproxy.io/docs/envoy/v1.19.0/configuration/listeners/network_filters/postgres_proxy_filter) and StartTLS filter (see https://www.envoyproxy.io/docs/envoy/v1.19.0/api-v3/extensions/filters/network/postgres_proxy/v3alpha/postgres_proxy.proto.html how to use it). Source: over 3 years ago
Do you know an article comparing Envoy Proxy to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Envoy Proxy. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.