laravel-patterns

Keep controllers thin by delegating orchestration to service classes and single-purpose logic to action classes. Controllers receive validated form requests, call an action, and return an API resource response.

Use eager loading with the with() method to load relationships upfront, such as Order::with(['customer', 'items.product'])->paginate(25). This fetches related models in a constant number of queries instead of one per record.

Scoped bindings enforce parent-child relationships in nested routes using Route::scopeBindings(). A child model like {project} is only resolved if it belongs to the parent {account}, preventing cross-tenant data access.

Create a form request class extending FormRequest with authorize() and rules() methods. Add a toDto() method to transform validated input into a data transfer object passed to your action or service layer.

Use queued jobs for slow work like reports, exports, and webhooks, and emit domain events for side effects such as emails and analytics. Handlers should be idempotent with retries and backoff configured.

Use either a global scope or a named scope for the same filter, not both, unless you intend layered behavior. Global scopes apply default filtering automatically, while named scopes like scopeOwnedBy are applied explicitly in queries.