use-clean-architecture

Summary

Adopt Clean Architecture to organize code into concentric layers, ensuring that dependencies only point inward. This separates business logic from external concerns like the CLI, Database, or API.

Rationale

• Separation of Concerns: Business logic is independent of UI, Database, and Frameworks.
• Testability: Business rules can be tested without external elements.
• Maintainability: Changes in external libraries or tools do not affect the core logic.

Guidance

Organize your project into the following directory structure:

1. Domain (internal/domain)

Contains Entities (Enterprise Business Rules) and Repository Interfaces.

• Dependencies: None.
• Content: Pure Go structs and interfaces.