backend-coding-guidelines

To prevent business logic from leaking in Laravel, enforce a strict 7-layer architecture separating Presentation, Request, UseCase, Service, Repository, Model, and Resource layers. This ensures clean separation of concerns and keeps controllers and models thin.

The best way to structure a Laravel backend for consistency is applying a standardized 7-layer pattern with UseCase, Repository, DTO, Service, and Resource components. This provides clear dependencies, validation rules, and naming conventions across all projects.

To implement the Repository pattern and DTOs in Laravel, define a UseCase with a Repository Interface, create a matching Laravel Data DTO, and use a FormRequest for validation. Wire these components into a Controller to complete the standardized backend feature.

TypeScript type generation is promoted alongside Laravel Data DTOs to enable strong typing and easier testing. Generating TypeScript types from DTOs provides a reliable contract between backend services and frontend clients.

Yes, the 7-layer Laravel architecture fully supports database transactions and testability. It includes detailed guidelines for transaction handling and DTO design specifically to ensure teams can build and refactor backend features reliably with strong typing.

You should avoid a strict 7-layer UseCase architecture for simple Laravel projects lacking complex business logic. The overhead of defining UseCases, Repositories, and DTOs is designed for large applications requiring strict separation of concerns and long-term maintainability.