ContextQMD
Back to Gofr

Learn GoFr

docs/learn/page.md

1.56.53.2 KB
Original Source

Learn GoFr

{% answer %} 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. {% /answer %}

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:

  1. Quick Start: Build your first GoFr REST API — get something running.
  2. Pick your migration guide:
  3. Configuration — environment-driven config.
  4. Connecting MySQL and Connecting Redis.
  5. Observability — see traces, metrics, and structured logs.
  6. 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.

  1. Why GoFr? — the philosophy and what's actually in the box.
  2. GoFr vs your current framework — head-to-head feature comparison.
  3. Quick Start: Build your first GoFr REST API.
  4. Auto CRUD REST handlers.
  5. Custom middleware.
  6. Service-to-service HTTP.
  7. 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.

  1. Observability.
  2. Custom OpenTelemetry spans.
  3. Custom Prometheus metrics.
  4. Service health monitoring.
  5. Authentication and RBAC.
  6. Circuit breaker support and HTTP communication.
  7. Database migrations.
  8. Startup hooks.
  9. Remote log level change.
  10. Profiling (pprof).
  11. Testing.

Reference materials