Why doesn't Laravel actively support Service Classes?

Question

There must be a good reason for this. Laravel's default pattern makes no use of Service Classes... but the Laravel community's best practices is for business logic to be stored in them.

Laravel's default pattern seems to break SRP, and there's no Artisan command for creating a service class, or even any reference to using them in Laravel's documentation.

This is obviously a very conscious decision by Taylor Otwell. So why did he do it? There must be a clear reason. Does Laravel not concern itself with SOLID?

Answer 1

Laravel is an implementation of the Model-View-Controller design pattern. The MVC design pattern does not include the idea of a "service class". Business logic and data access is crammed into the "Model" part of MVC. This part of the design pattern is loosely defined. The most important thing to remember with MVC is that it is a user interface design pattern, not an all-inclusive architecture. How to organize business logic and data access logic is outside the scope of the MVC design pattern, and therefore outside the scope of the Laravel framework.

The Laravel community might be leaning towards service classes for organizing business logic, but that is subjective and depends on the complexity of logic, among many other things. Other design patterns and techniques like Clean Architecture, Onion Architecture and Domain Driven Design focus on the bigger picture of how code is organized and architected, and this may include utilizing MVC for the user interface portion of the application.