[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fh46csx6doako":3},{"code":4,"message":5,"data":6,"timestamp":51},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":27,"summary_md":28,"topic":29,"github_topics":32,"license":41,"homepage":42,"updated_at":43,"history":44},"envoyproxy\u002Fenvoy",12,"Cloud-native high-performance edge\u002Fmiddle\u002Fservice proxy","C++",29129,5682,11,3729,[16,22],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},41109903,"Envoy WASM extensions in the present and its future (Proxy-WASM)",2,0,"2024-07-30",{"id":23,"title":24,"points":25,"comments":20,"posted_at":26},47851699,"Envoy Proxy: high-performance, open-source edge and service proxy",1,"2026-04-21","A high-performance proxy giving platform teams one data plane for routing, observability and policy across services and edges.","Envoy is worth your time if you operate service-to-service or edge traffic and need one programmable hop between clients and backends. It is less appealing if you want something you can hand-wire in an afternoon without a control plane.\n\n## The problem\n\nA team running many services wants consistent routing, retries, telemetry and access policy instead of reimplementing them in each application. Traditionally that logic lives in libraries or per-service config, so a routing change or a new observability requirement becomes a code change and a deployment per service. With Envoy, that logic moves into a separate proxy process in front of workloads; operations changes become proxy configuration rather than application releases. The result is a uniform traffic layer, at the cost of running and configuring another component in the path.\n\n## What's different\n\nEnvoy's distinguishing idea is a universal, dynamic data-plane API: configuration can be pushed to the proxy instead of edited by hand and restarted. The README points to the universal data plane API design write-up and a related data-plane-api project, which is what lets control planes drive many proxies consistently. The proxy also exposes a documented stats architecture and hot restart, both explained in linked design posts, so traffic handling and process lifecycle are treated as first-class operational concerns. These matter when you change routes or roll proxies while traffic is live.\n\nThat design has a real price. Envoy is an infrastructure component with its own configuration model, and the interesting work usually involves a separate control plane to generate and push config. The project also documents that ppc64le builds are best-effort and outside the security policy, so choosing an unusual architecture changes your support expectations. It is a proxy, not an application framework: if your problem is writing business logic, this is the wrong layer.\n\n## Who should try it\n\nGood fit: platform or infrastructure teams that already accept a sidecar or gateway model and want one proxy behaviour across services, with config driven by a control plane and telemetry collected centrally. Also a fit for edge gateway use where you need routing and policy ahead of backend services. Poor fit: a small application team that wants a single binary for local development routing, or anyone unwilling to own proxy configuration and upgrades. Teams without a control plane should check whether the documented static configuration path covers their needs before investing.\n\n## Requirements and limitations\n\nYou need to operate a proxy in the traffic path, which means capacity planning, config validation and an upgrade routine for a component whose failure affects requests. Dynamic configuration assumes tooling to produce and deliver it; the README links the data-plane API rather than an all-in-one management server. Platform support is uneven: ppc64le builds are explicitly best-effort and not covered by the security policy, while other builds are listed separately. Security response is organised through GitHub Security Advisories and a documented release process, so you should track security announcements and plan upgrades rather than treating a deployed version as finished.\n\n## HotRepo's take\n\nHotRepo's recorded sample is tiny: Envoy appeared on the daily board on 2026-10-24 and 2026-10-25, at 29,124 and 29,127 stars (+9 and +11). That is a snapshot of a long-established project, not evidence about momentum, so persistence cannot be judged from it. Before adopting, verify the specific platform and configuration path you need against the [official documentation](https:\u002F\u002Fwww.envoyproxy.io\u002F) and the [FAQ](https:\u002F\u002Fwww.envoyproxy.io\u002Fdocs\u002Fenvoy\u002Flatest\u002Ffaq\u002Foverview).",{"slug":30,"name":31},"devops","DevOps & Self-hosting",[33,34,35,36,37,38,39,40],"cars","cats","cats-over-dogs","cncf","corgis","more-cats","nanoservices","rocket-ships","Apache-2.0","https:\u002F\u002Fwww.envoyproxy.io","2026-10-25T03:20:04Z",[45,49],{"date":46,"stars":47,"stars_gained":48},"2026-10-24",29124,9,{"date":50,"stars":11,"stars_gained":13},"2026-10-25",1792909411]