I used the solution to build a project's proxy server and load balancer.
Pros
"I found Envoy simple to use compared to alternatives like Traefik.
"
Cons
"The tool needs to incorporate better documentation and more example samples.
"
As on the ground microservice practitioners quickly realize, the majority of operational problems that arise when moving to a distributed architecture are ultimately grounded in two areas: networking and observability. It is simply an orders of magnitude larger problem to network and debug a set of intertwined distributed services versus a single monolithic application.
Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures. Built on the learnings of solutions such as NGINX, HAProxy, hardware load balancers, and cloud load balancers, Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place.
I used the solution to build a project's proxy server and load balancer.
I found Envoy simple to use compared to alternatives like Traefik.
The tool needs to incorporate better documentation and more example samples.
I haven't contacted the tool's support team.
I chose Envoy for the POC because it was easier to integrate with our project than Traefik. We used gRPC services and microservices and needed to build a gateway, reverse proxy, and load balancing. Envoy helped accomplish this successfully and quickly.
I only used Envoy for a proof-of-concept project, so I didn't deploy it in production.
The tool is open-source.
Envoy is easy for beginners for small use cases but might get more complex for complicated setups. Based on my limited experience, I'd rate it a nine out of ten for how well it worked for my specific use case.
