Laravel API: Service layer vs Actions – what scales better?

[blactelin]

I'm building REST APIs with Laravel and trying to keep controllers thin.

What do you prefer for scalable projects:

• Service classes
• Action / UseCase pattern
• Or a hybrid approach?

Would love to hear real-world experience.

[blac98]

In my experience, a hybrid approach works best for scalable Laravel APIs.

I usually keep controllers very thin, delegate business logic to Service classes,
and use Actions (or UseCases) for specific workflows like onboarding, payments, etc.

Form Requests for validation + DTOs also help keep things clean as the project grows.

[blactelin]

Thanks! That hybrid approach makes a lot of sense.
Especially like the idea of using Actions for complex workflows.

[blac98]

Glad it helped! This pattern has worked well for me on larger codebases.

[blactelin]

Thanks, this is really helpful.
I like how you combine Services with Actions in real projects.