// the find
go-eagle/eagle
🦅 A Go framework for the API or Microservice
Eagle is a Go microservice framework that wires together Gin, gRPC, GORM, Zap, and a dozen other common libraries into an opinionated project skeleton with a CLI generator. It targets teams who want a batteries-included starting point for Chinese-market Go services rather than assembling their own stack. The companion `eagle` CLI generates handlers, repositories, protos, and cache layers from templates.
The layered architecture (handler → service → repository → dal) is cleanly enforced and the directory conventions are sensible — a new team member will know where to look for things. The CLI code generators are a genuine time-saver: `eagle new` scaffolds a full project and `eagle add handler` keeps the layer boundaries intact. OpenTelemetry tracing, Prometheus metrics, and structured Zap logging are wired in from day one, not bolted on later. The examples directory covers real use cases — Kafka, RabbitMQ, Redis queue, gRPC, cron — with runnable code rather than pseudocode snippets.
The project is primarily maintained for Chinese users (docs, community, and issue tracker lean heavily Chinese), which creates a real support gap for anyone else hitting a non-obvious problem. The framework is largely a thin assembly of other libraries with light glue — when something breaks inside GORM or go-redis, you're debugging the underlying library anyway, and Eagle adds a layer of indirection that makes that harder. Wire-based dependency injection is referenced in the architecture diagram but not meaningfully demonstrated in the main scaffolding, so you get the ceremony without much of the benefit. Test coverage outside the pkg utilities is thin; the example app has no integration tests, so the 'rapid business development' promise comes with unknown production edge cases.