News for hackers. Stuff that matters.

A comment on Envoy: Modern Proxy server with HTTP 1.1 and 2, GRPC supported reverse proxy. Parent comment

Re:Envoy: Modern Proxy server with HTTP 1.1 and 2, GRPC supp... by devmunchies on Thursday September 28, 2017 @09:49AM (#15357079)
Lyft already took care of that: https://hub.docker.com/r/lyft/envoy/
[ Parent | on HN ]
Re:Envoy: Modern Proxy server with HTTP 1.1 and 2, GRPC supp... by nevi-me on Thursday September 28, 2017 @12:27PM (#15358422)
Would one use this container as a base? I've tried learning Docker, but I often end up *just referring back to LXD when I get confused.

If I wanted to run a Python app, which serves gRPC, what would be the easiest path?

I currently use nghttp2 for gRPC proxy/routing

[ Parent | on HN ]
Re:Envoy: Modern Proxy server with HTTP 1.1 and 2, GRPC supp... by ianburrell on Thursday September 28, 2017 @01:27PM (#15359070)
It is better to run components in separate containers instead of one container that runs everything together. You'll likely have a single proxy but multiple copies of application. Also, you don't need to deal with getting Envoy and Python application built together, or even care about how the Envoy image is built since you can use the provided one.
[ Parent | on HN ]