backend-guidelines

Backend architecture guidelines define clear module and layer responsibilities, such as Domain, Use Case, PBLC, Infra, and Controller, to ensure strict separation of concerns across all backend features.

You can implement the Unit of Work and repository patterns by following centralized backend guidelines that provide specific templates, transaction management rules, and examples for consistent data access and cross-module interactions.

To enforce consistent error handling conventions across backend modules, apply a centralized set of backend development standards that define robust error handling rules, such as using errx, across the entire project.

The document-first workflow requires you to document the intended use case before implementing any backend feature, ensuring compliance with architecture rules, error handling, and Unit of Work practices from the start.

Yes, these backend guidelines apply to database migrations and testing standards by providing specific templates, testing rules, and architecture conventions to ensure testable designs and consistent implementation across modules.

You should reconsider a layered backend architecture if your project does not require strict module separation, complex transaction management, or cross-module interactions, as the guidelines enforce heavy standards like Unit of Work and document-first workflows.