laravel-ops

# Laravel Operations > Facts verified as of 2026-07. Authoritative reference for Laravel 11+ development: architecture decisions, Eloquent patterns, authentication strategies, queue configuration, and testing approaches. --- ## Architecture Decision Tree ``` What type of application? │ ├─ Full-stack web (HTML responses) │ ├─ Simple CRUD, small team → Monolith (Blade + Eloquent directly) │ │ └─ Use action classes for business logic over 20 lines │ ├─ Rich interactivity needed → Livewire (server-driven reactivity) │ │ └─ Add Alpine.js for client-side micro-interactions │ └─ SPA-like feel, React/Vue team → Inertia.js │ └─ Keep server-side routing, dump client-side routing overhead │ ├─ API backend (JSON responses) │ ├─ Single consumer (mobile/SPA) → API-only with Sanctum SPA auth │ ├─ Multiple consumers / public → RESTful API with token auth │ └─ Complex graph queries → Consider GraphQL (lighthouse-php/lighthouse) │ ├─ Large team / complex domain │ ├─ Domain-driven → Modular monolith (app/Modules/{Domain}/) │ │ ├─ Each module: Models, Actions, Events, Jobs, Http/ │ │ └─ Shared: app/Shared/ for cross-cutting concerns │ └─ Independent deployability needed → Microservices │ └─ Use Laravel Octane for high-throughput services │ └─ What business logic pattern? ├─ Simple CRUD, < 20 lines → Direct Eloquent in controller ├─ Reusable operation (create order, send invoice) → Action class │ └─ Single public handle() or execute() method ├─ Com...