go-standard-package-layout

Structure Go codebases by placing domain core logic in the root package, creating dependency-named subpackages for external concerns, and wiring components explicitly in the main package to improve maintainability and testability.

Ben Johnson's standard package layout organizes Go applications by keeping pure domain logic in the root package, isolating external concerns in dependency-named subpackages, and using a shared mock package for testing without external frameworks.

Keep domain logic separate by placing pure domain types and logic in the root package, then creating subpackages named after each external dependency to isolate integration points, ensuring the core remains free of external concerns.

No, this Go package layout does not require external testing frameworks. It uses a shared mock package to simplify testing, allowing you to test domain logic and dependencies without adding third-party testing dependencies.

The best way to wire Go components for predictable builds is explicit composition in the main package. This standard package layout approach assembles all dependency-named subpackages and domain core in one place for clear, predictable dependency injection.

Use a domain-core package layout when your Go application needs scalable structure and testability. It enforces clear placement, naming, and wiring rules, making it ideal for projects where separating pure domain logic from external integration points is critical.