Gone
A lightweight dependency injection framework for Go with tag-based auto injection, config center support, and rich ecosystem components.
What is Gone?
Gone is a lightweight dependency injection framework for Go that uses Golang struct field tags to manage component dependencies through concise annotations. It simplifies building modular and maintainable applications by automating dependency resolution and lifecycle management, enabling developers to focus on business logic rather than boilerplate wiring.
Go developers building modular, maintainable applications who want to reduce boilerplate code for dependency management, particularly those working on services that require integrated configuration, logging, database, or LLM components.
Developers choose Gone for its tag-based auto-injection that supports private fields and configuration values, integrated lifecycle management with start/stop hooks, and a rich ecosystem of pre-built components (goner) for common needs like observability and databases, all emphasizing convention over configuration.
Overview
🚀 Gone - A Lightweight Dependency Injection Framework for Go | Tag-based Auto Injection | Supports Config Center/Lifecycle Management | Provides Rich Ecosystem Components and Scaffolding Tool
Use Cases
Best For
- Implementing dependency injection in Go applications with minimal boilerplate using struct tags.
- Managing component lifecycles (initialization, start, stop) automatically in Go services.
- Injecting configuration from multiple sources (environment variables, config files, external config centers) into Go structs.
- Integrating pre-built components for logging, database, LLM, and observability in Go projects.
- Scaffolding new Go projects with dependency injection setup using the included gonectl tool.
- Mocking dependencies for testing in Go applications via the gonectl tool's code generation features.
Not Ideal For
- Projects with minimal dependencies where manual wiring is simpler and more transparent
- Teams already using compile-time DI frameworks like Google Wire, as Gone's runtime injection offers less early error detection
- Developers who prefer explicit, code-first dependency management without tag-based 'magic' annotations
- Legacy Go applications with established wiring patterns, where migrating to Gone's conventions would be disruptive
Pros & Cons
Pros
Uses Golang struct tags like `gone:"*"` for automatic dependency injection, reducing boilerplate code as shown in the README example with private field support.
Provides Init(), start, and stop methods with hooks for automated service management, simplifying component orchestration without manual wiring.
Offers pre-built goner components for logging, database, LLM, and observability, accelerating development with ready-to-use modules from the goner repository.
Includes gonectl for project creation, code generation, and test mocking, streamlining setup and maintenance as demonstrated in the quick start guide.
Cons
Dependency resolution via tags occurs at runtime, which can hide misconfigurations or missing dependencies until execution, unlike compile-time DI solutions.
Requires installing gonectl and mockgen separately for full functionality, adding setup complexity and potential environment friction.
As a newer framework, it has fewer third-party integrations, tutorials, and community support compared to established alternatives like Uber's dig.
Frequently Asked Questions
Related Projects
GinGin is a high-performance HTTP web framework written in Go. It provides a Martini-like API but with significantly better performance—up to 40 times faster—thanks to httprouter. Gin is designed for building REST APIs, web applications, and microservices.
EchoHigh performance, minimalist Go web framework
Beegobeego is an open-source, high-performance web framework for the Go programming language.
GoFrAn opinionated GoLang framework for accelerated microservice development. Built in support for databases and observability.
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.