go-architecture

Place binaries under cmd/<name>/main.go and service logic under internal/, which the Go toolchain prevents other modules from importing. Keep main thin as a composition root, isolate generated database code in a store package, and avoid adding a pkg/ directory out of habit.

Start with the stdlib net/http ServeMux, which since Go 1.22 supports method matching and path wildcards like GET /posts/{id}. Move to chi when you need route groups and middleware while staying net/http-native; choose echo or gin only if you want their batteries, and fiber only for measured throughput needs.

sqlc with the pgx driver is the current default for new services because it generates type-safe Go from raw SQL without reflection or hidden queries. GORM remains viable for rapid CRUD scaffolding or teams already fluent in it, so migrate only with cause.

No, idiomatic Go uses constructor injection where each component accepts its dependencies as interface parameters and main wires them explicitly. Add google/wire for compile-time codegen only when manual wiring genuinely hurts, and prefer it over runtime containers like uber/fx.

A pgxpool.Pool is safe for concurrent use and should be shared across handlers, while a single *pgx.Conn is not concurrency-safe. Create the pool with pgxpool.New in main and pass it to your store constructors.

Do not use it for concurrency patterns with goroutines and channels, general language idioms, or testing and benchmarking, which belong to separate skills. It also does not apply to non-Go backends like Laravel, Next.js, or Rust.