How does Envoy compare to Nginx and HAProxy, and when would you choose Envoy over them?

Think of Nginx and HAProxy as experienced highway toll operators who are extremely efficient at directing traffic along pre-planned routes. Envoy is more like a GPS navigation system that continuously recalculates routes based on real-time traffic conditions, road closures, and new destinations appearing on the map. Both approaches work, but they excel in different scenarios.

Nginx was originally built as a high-performance web server and reverse proxy, optimized for serving static content and handling large numbers of concurrent connections. HAProxy was purpose-built as a load balancer with exceptional performance for TCP and HTTP traffic. Both tools use static configuration files that require a reload or restart when changes are made. While Nginx Plus and newer HAProxy versions have added some dynamic capabilities, their core architecture is fundamentally file-driven. Envoy, by contrast, was designed from day one with dynamic configuration as a first-class feature. Its entire configuration, including listeners, routes, clusters, and endpoints, can be updated at runtime through the xDS API without any restarts or connection drops.

The protocol support is another major differentiator. Envoy natively supports HTTP/1.1, HTTP/2, and gRPC as first-class protocols, with the ability to translate between them. For example, Envoy can accept an HTTP/1.1 request from a legacy client and forward it as HTTP/2 to the upstream service, or proxy gRPC traffic with full understanding of the protocol semantics. Nginx added HTTP/2 support later, and HAProxy's gRPC support is more limited. Envoy also supports advanced L7 protocols through its extensible filter chain, including MongoDB, MySQL, Redis, and Thrift protocol awareness, allowing it to parse and route application-specific traffic.

In terms of observability, Envoy generates detailed statistics for every upstream cluster, downstream connection, and individual request. It natively integrates with distributed tracing systems by propagating trace context headers and generating spans. It exports metrics in formats compatible with Prometheus, StatsD, and other monitoring backends. Nginx and HAProxy provide access logs and basic metrics, but they require additional modules or external tools to achieve the level of observability Envoy provides out of the box. Envoy's admin interface exposes runtime configuration, cluster health, statistics, and debugging endpoints, making it significantly easier to troubleshoot in production.

Choose Envoy when you are building a microservices architecture with dynamic service discovery, need a service mesh data plane, require native gRPC support, or need rich observability without additional tooling. Choose Nginx when you need a high-performance web server for static content, a well-established reverse proxy with extensive module ecosystem, or when your team has deep Nginx expertise. Choose HAProxy when you need a battle-tested TCP/HTTP load balancer with deterministic performance characteristics and simpler operational requirements. In practice, many organizations use Envoy as a sidecar proxy alongside Nginx or HAProxy at the edge, combining the strengths of each tool in different layers of their architecture.