laravel-patterns

Topics in the source

• Laravel Development Patterns
• When to Use
• How It Works
• Examples
• Project Structure
• Recommended Layout
• Controllers -> Services -> Actions
• Routing and Controllers

Production-grade Laravel architecture patterns for scalable, maintainable applications. Building Laravel web applications or APIs Structuring controllers, services, and domain logic Working with Eloquent models and relationships Designing APIs with resources and pagination Adding queues, events, caching, and background jobs Structure the app around clear boundaries (controllers -> services/actions -> models). Use explicit bindings and scoped bindings to keep routing predictable; still enforce authorization for access control. Favor typed models, casts, and scopes to keep domain logic consistent. Keep IO-heavy work in queues and cache expensive reads. Centralize config in config/ and keep environments explicit. Use a conventional Laravel layout with clear layer boundaries (HTTP, services/actions, models). Keep controllers thin. Put orchestration in services and single-purpose logic in actions. Prefer route-model binding and resource controllers for clarity. Use scoped bindings to prevent cross-tenant access. Keep prefixes and paths consistent to avoid double nesting (e.g., conversation vs conversations). Use a single parameter name that matches the bound model (e.g., {conversation}

This is an excerpt. Refer to the complete source and its current requirements.