Go project structure and package layout #6

New issue

Open

opened 2026-08-23 11:17:16 +02:00 by gaetan · 0 comments

gaetan commented

2026-08-23 11:17:16 +02:00

Owner

Part of #1

Question

Design the Go project structure following Clean Architecture principles. Key decisions:

Package layout: How to organize the codebase — by layer (handler/service/repository) or by domain (book/user/auth)?
Dependency injection: How to wire dependencies — manual wiring in main.go or a DI container?
Configuration: How to load config (env vars, .env file, config file)?
Error handling: Global error types? Custom error wrapping?
Testing strategy: Table-driven tests? Mock interfaces? Testcontainers for SQLite?

Consider the Clean Architecture convention from CLAUDE.md: entities → use cases → interface adapters → frameworks.

Example structure to evaluate:

cmd/
  server/
    main.go
internal/
  domain/
    book.go
    user.go
  usecase/
    book_usecase.go
  adapter/
    http/
      book_handler.go
    repository/
      book_repo.go
  config/
    config.go

Part of #1 ## Question Design the Go project structure following Clean Architecture principles. Key decisions: - **Package layout**: How to organize the codebase — by layer (handler/service/repository) or by domain (book/user/auth)? - **Dependency injection**: How to wire dependencies — manual wiring in `main.go` or a DI container? - **Configuration**: How to load config (env vars, .env file, config file)? - **Error handling**: Global error types? Custom error wrapping? - **Testing strategy**: Table-driven tests? Mock interfaces? Testcontainers for SQLite? Consider the Clean Architecture convention from CLAUDE.md: entities → use cases → interface adapters → frameworks. Example structure to evaluate: ``` cmd/ server/ main.go internal/ domain/ book.go user.go usecase/ book_usecase.go adapter/ http/ book_handler.go repository/ book_repo.go config/ config.go ```

gaetan added the

wayfinder:grilling

label

2026-08-23 11:17:16 +02:00

gaetan added a new dependency

2026-08-23 11:17:38 +02:00

#2 Design the database schema