New framework for Go (Golang) gains popularity: what developers need to know
The ecosystem of the Go programming language (Golang) continues to actively develop. In 2025, the community noticed a sharp surge of interest in a new framework that promises to change the approach to building web applications and microservices. We are talking about the project Fuego — a lightweight, high-performance framework that is already being called the "Gin and Echo killer."
Fuego appeared at the end of 2024 as an open-source initiative by a group of enthusiasts from Europe. In a few months, it surpassed many mature projects in terms of GitHub star growth rate. Currently, Fuego has over 8,000 stars, and the number of commits doubles every month. So what attracted developers?
Key features of Fuego
- Zero-allocation routing — routing without unnecessary memory allocations, providing a performance boost of up to 40% compared to Gin.
- Built-in support for OpenAPI 3.1 — documentation is generated automatically from code, without third-party utilities.
- Native work with Go 1.22 contexts — the framework uses new features of the standard library, simplifying request management.
- Modular architecture — the developer can connect only the necessary components (middleware, validators, loggers) without overloading the project.
- Built-in hot-reload — code changes are applied instantly, without restarting the binary.
Why is Fuego gaining popularity right now?
The main reason is community fatigue with cumbersome solutions. Gin, Echo, and Chi remain reliable, but their APIs have barely changed in the last 5 years. Developers want:
- less boilerplate;
- more automation (client generation, documentation);
- better integration with modern tools (Docker, Kubernetes, gRPC).
Fuego solves these problems. For example, to create a REST API with documentation, just 15 lines of code are enough:
package main
import "github.com/go-fuego/fuego"
func main() { s := fuego.NewServer() fuego.Get(s, "/hello", func(c fuego.ContextNoBody) (string, error) { return "Hello, World!", nil }) s.Run()}When launched, the framework automatically generates swagger.json and starts a UI for testing endpoints.
Comparison with competitors
| Framework | OpenAPI | Hot-reload | Performance (req/s) |
|---|---|---|---|
| Fuego | Built-in | Yes | ~85 000 |
| Gin | Requires Swaggo | No | ~70 000 |
| Echo | Requires third-party libs | No | ~65 000 |
Prospects and community opinion
Lead developer of Fuego, Mark Schmidt, stated at the GopherCon Europe 2025 conference: "We are not trying to replace Gin. We want to show