Home / Companies / Ambassador / Blog / Post Details
Content Deep Dive

Envoy vs NGINX vs HAProxy: Why the Edge Stack API Gateway chose Envoy

Blog post from Ambassador

Post Details
Company
Date Published
Author
-
Word Count
1,307
Company Posts That Month
1
Language
English
Hacker News Points
-
Post removed?
No
Summary

The Edge Stack API Gateway chose Envoy as its core proxy due to its feature set, which is well-suited for a Layer 7 (L7) world where business logic is distributed across ephemeral microservices. Envoy was designed from the ground up for this L7, services-oriented world and has features such as hitless reloads, observability, resilience, and advanced load balancing. The Envoy community is unique, with no commercial pressure to create proprietary editions, allowing it to focus solely on building the best possible L7 proxy. Envoy's forward-thinking vision, rich feature set, and rapid pace of innovation have made it an ideal choice for Edge Stack API Gateway.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 3 61 23 12 -46%
Kubernetes 2 612 67 26 +53%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.