// the take
A Go-based API gateway from Apache that translates HTTP and gRPC requests into Dubbo protocol calls, letting non-Java clients talk to Dubbo clusters without rewriting them. Recently repositioned itself as an 'AI Gateway' for routing LLM traffic, though the Dubbo bridging is the actual battle-tested part. Primarily useful if your backend is already running dubbo-go or Dubbo Java services.
- Protocol translation from HTTP/gRPC to Dubbo2 and Triple is genuinely hard and this is the official Apache solution for it — if you're in that stack, there's no obvious alternative
- Kubernetes Ingress Controller is a real addition (controllers/ has its own go.mod, CRD types, and reconciler logic), not just a doc claim
- Service discovery integration with Zookeeper and Nacos is first-class, not an afterthought — important in typical Dubbo deployments
- Apache governance shows: proper CI, .asf.yaml, .licenserc.yaml, and a structured PR review flow synchronized to both a fork repo and the Apache upstream
- 554 stars for an Apache-backed gateway competing with Envoy, Kong, and Traefik signals narrow adoption — this is a Dubbo-ecosystem tool that doesn't translate well outside it
- The 'AI Gateway' pivot reads as marketing; the README is now full of LLM buzzwords but the actual AI feature surface (configs/ai_kvcache_config.yaml, docs/ai/) looks shallow compared to purpose-built LLM proxies
- Admin UI is a separate Vue 2 + Element UI frontend living in admin/web with its own build chain and a yarn.lock — running the full stack locally involves coordinating three separate systems (gateway, admin Go backend, Vue frontend)
- English documentation is a translation layer over Chinese-first docs; _CN.md files are the primary versions and the English equivalents visibly lag, which is a real friction point for non-Chinese teams evaluating adoption
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →