backend-guidelines

A Go backend project should use layered architecture with repositories and Unit of Work (UOW) transactions. You implement features bottom-up, defining repository interfaces and use cases while ensuring layer boundaries and cross-module import rules are never violated.

Guidelines for writing use cases and controllers specify strict layer responsibilities, API design standards, and coding conventions. You document first, implement the logic layer-by-layer, and test everything to maintain enterprise blueprint compliance.

To handle errors using the errx pattern, you apply standardized error handling conventions defined for your Go backend. This ensures consistent error wrapping and responses across all internal modules without violating architectural layer rules.

You write system tests and migrations for Go applications by following standardized conventions. Migrations are handled using goose, while system tests must cover all implemented features, ensuring every layer is tested before deployment.

Yes, repogen is used for repository creation within the Go backend architecture. You apply the repogen pattern alongside UOW transaction management to standardize data access layers while keeping module imports strictly separated.

Before making code changes to a Go backend codebase, you should review the project's architecture rules, API design, and coding standards. Documenting first and implementing bottom-up ensures compliant design and prevents layer boundary violations.