▲ 13 r/laravel
How do you structure service classes in larger Laravel projects?
I’ve worked on a few Laravel projects where controllers became too heavy over time, especially when the app had payments, notifications, reports, third-party APIs, and admin workflows.
Recently I’ve been trying to keep controllers very thin and move business logic into service classes.
Example structure:
app/
Services/
Payments/
Notifications/
Reports/
Tenants/
Actions/
DTOs/
For simple CRUD, I still keep things straightforward. But for complex workflows, I feel service classes make the code easier to test and maintain.
Curious how others here usually structure larger Laravel apps.
Do you prefer service classes, actions, jobs, repositories, or just keeping logic closer to models/controllers?
u/aliRazaLilani — 3 days ago