// the find
easegress-io/easegress
A Cloud Native traffic orchestration system
Easegress is a Go-based traffic orchestration system that ships an embedded etcd cluster for Raft-based HA — no external coordination service required. It covers API gateway, reverse proxy, load balancing, service mesh sidecar, and Kubernetes ingress from a single binary with a pipeline/filter composition model. Target audience is teams who want one thing to configure instead of Nginx + Consul + a circuit breaker library.
The embedded etcd approach is genuinely useful: you get clustering and config replication without running a separate control plane, and the Raft leader election story is straightforward to reason about. The pipeline/filter model is flexible in practice — you compose JWT verification, rate limiting, and canary splitting as declarative YAML stages rather than writing middleware glue code. Hot-reload of both config and binary without dropping connections is operationally valuable and not something most alternatives offer without ceremony. WebAssembly filter support means you can extend behavior without forking and recompiling.
The embedded etcd is also the main operational headache: you need three nodes minimum for real HA, Raft adds disk I/O pressure from WAL writes, and debugging split-brain scenarios in etcd is not fun. At ~5.9k stars it's competing directly against Envoy (25k+), Traefik (50k+), and Kong in a space where community size translates directly into Stack Overflow answers and maintained third-party integrations — adoption here is thin. The service mesh story leans on EaseMesh (a separate project) for the sidecar model, so it's not self-contained the way Istio/Linkerd are. The AI gateway features appear recent and the docs for them are sparse relative to the core proxy functionality, which raises questions about production readiness there.