// the take
YoyoGo is a dependency-injection-first microservice framework for Go, bundling routing/MVC, multiple HTTP server backends (net/http, fasthttp, gRPC), and built-in clients for Nacos, Consul, Etcd, Eureka, and Kubernetes service discovery. It's aimed at teams building Go microservices who want a batteries-included alternative to assembling go-kit/go-chi/grpc-go by hand, particularly in environments already standardized on one of those discovery backends.
The service-discovery abstraction is genuinely broad — swapping Nacos for Consul or Etcd is a config change, not a rewrite, which is unusual since most Go frameworks pick one and stick to it. DI is load-bearing rather than bolted on: controllers, middleware, and MVC actions are constructor-injected, and the server layer itself (fasthttp vs net/http vs grpc) is abstracted behind the same builder. It ships the operational stuff people usually add later as separate libraries: Prometheus metrics, health checks, JWT middleware, and swagger generation from struct tags. The yygctl CLI scaffolds a working project rather than leaving you to copy an example by hand.
Last push was April 2024 — over two years stale as of now, which matters for a framework whose whole value is staying in sync with Nacos/Consul/Etcd/Eureka client protocol changes and k8s API versions. Primary community and support channel is a QQ group and WeChat account; the English README is a secondary translation and the docs site (dev.yoyogo.run) is Chinese-first, so non-Chinese-speaking teams will hit a wall when something breaks. At 582 stars it's nowhere near the production mileage of go-kit, go-micro, or Kratos, so expect to find your own edge cases rather than finding them already filed. It integrates a lot of surface area in one dependency tree — redis, mysql, email, captcha, xxl-job scheduler, multiple discovery clients — which means a vulnerability or breaking change in any one upstream (e.g. the etcd or nacos client) becomes your problem even if you only wanted the HTTP router.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →