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.
| Product | Market Share (%) |
|---|---|
| Envoy | 21.4% |
| Istio | 20.5% |
| Kong Mesh | 18.7% |
| Other | 39.400000000000006% |
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.
| Author info | Rating | Review Summary |
|---|---|---|
| Full-stack Developer at ImageVision.ai | 4.5 | I used Envoy to build a project's proxy server and load balancer because it was easier to integrate than Traefik. Despite its simplicity and effectiveness, Envoy needs better documentation and more examples to improve usability. |
