Learn GoFr
Summary
There's no single right way to learn a framework — the best path depends on where you're starting from. Three tracks below sequence the existing GoFr documentation by background and goal: coming from another language, experienced Go developer new to GoFr, or building for production.
Track A — Coming from another language
Estimated time: 1–2 hours (read) + 30 min (run hello-world).
You know how to build microservices in Node, Python, Java, or another ecosystem, but you're new to Go. Read in this order:
- Quick Start: Build your first GoFr REST API — get something running.
- Pick your migration guide:
- Configuration — environment-driven config.
- Connecting MySQL and Connecting Redis.
- Observability — see traces, metrics, and structured logs.
- GoFr Context Reference — the one core abstraction.
Track B — Go developer new to GoFr
Estimated time: 30 min (read) + 30 min (run hello-world).
You've written Go before — maybe with net/http, Gin, Fiber, Echo, or Chi.
- Why GoFr? — the philosophy and what's actually in the box.
- GoFr vs your current framework — head-to-head feature comparison.
- Quick Start: Build your first GoFr REST API.
- Auto CRUD REST handlers.
- Custom middleware.
- Service-to-service HTTP.
- GoFr Context Reference and Configuration Reference.
Track C — Building for production
Estimated time: 2–3 hours, dipping in as you encounter each concern in real services.
- Observability.
- Custom OpenTelemetry spans.
- Custom Prometheus metrics.
- Service health monitoring.
- Authentication and RBAC.
- Circuit breaker support and HTTP communication.
- Database migrations.
- Startup hooks.
- Remote log level change.
- Profiling (pprof).
- Testing.
Reference materials
- Full documentation index
- Examples repository
- Showcase — companies and engineers running GoFr in production.
- Changelog — release notes and version history.