// the take
Apache ShenYu is a Java API gateway built around a plugin chain, with a separate Admin service that owns routing/plugin config and pushes it to gateway replicas. It targets teams already running Spring Cloud, Dubbo, or gRPC microservices who want one gateway handling mixed protocols instead of bolting Nginx plus custom proxies together.
Protocol coverage goes beyond HTTP in a way most gateways don't: Dubbo and gRPC proxying are first-class, not an afterthought bolted on via a sidecar. The plugin chain plus SPI and WASM extension points mean custom auth/routing logic doesn't require a fork. Config sync isn't locked to one mechanism - ZooKeeper, Nacos, etcd and WebSocket are all supported, so it can slot into whatever discovery stack you're already running. It's a long-lived Apache project with an actual upgrade trail (DB migration scripts going back to 2.4.1) and CI/coverage, not a repo that's one maintainer's side project.
Admin's quickstart runs on an in-memory H2 database - durable, HA config storage is left entirely to the operator, and the docs don't walk through that production path. Several integrations (SOFA, Tars, Apollo, Consul, Hystrix) are actively being split out into separate plugin-store starters, so if you depend on any of those, you're adopting mid-migration and need to track which release moved what. It's a JVM process sitting in your request path purely for routing, which is heavier to run and tune (GC, thread pools) than something like Envoy or Traefik if your stack isn't already Java-based. Multi-tenant isolation and plugin config security (the quickstart's localKey auth) are primitives you have to build policy around yourself - WAF and signing plugins exist but don't give you that out of the box.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →