go-architecture

<objective> Structure Go 1.22+ backend services: the standard cmd/internal layout, choosing an HTTP router (net/http ServeMux, chi, echo/gin/fiber), constructor-based dependency injection, and type-safe database access with sqlc + pgx. Covers laying out a new Go project, choosing a router or DB layer, wiring dependencies, and reviewing an existing service's structure. Does not cover goroutines/channels concurrency patterns (see go-concurrency) or general language idioms (see go-core-idioms). </objective> # Go Architecture Opinionated, 2026-current guidance for structuring Go backend services. Favors the standard library and small, composable libraries over heavy frameworks. **Use when:** - Laying out a new Go module or service (directory structure, `cmd/`, `internal/`) - Choosing an HTTP router (stdlib `net/http` ServeMux, chi, echo/gin/fiber) - Choosing a database layer (sqlc + pgx, GORM) or wiring queries - Wiring dependencies (constructors, DI without a framework) - Reviewing an existing Go service for structural / architectural issues **Do NOT use for:** - Writing tests, benchmarks, fuzzing, coverage — use `go-testing-quality` - SOLID line-limit / interface-placement enforcement — use `fuse-solid:solid-go` - Non-Go backends (Laravel, Next.js, Rust) — use the matching expert - Frontend / UI work — use `fuse-design` or a framework expert --- ## Decision Map | Question | Load | |----------|------| | Where do files/packages go? | [project-layout.md](references/project-...