Laravel does not have anything like that. People have their own preferred pattern. Some use services, others actions, and some just use models directly from the controller (default usage). It is up to the developer to select the preferred pattern and implement it (perhaps using a package)
I also found this strange, because back in Laravel 3/4 I seem to remember a Laravel Service was a standard thing. I still use it now as it seems to be the logical solution to run an operation that can be called from either the controller or a cron job, or when multiple controllers need the ability to call the same proceedure it just seems to make sense to share a service rather than duplicate a function.
back in Laravel 3/4 I seem to remember a Laravel Service was a standard thing
@jimbocity Was it, though? I started working properly with Laravel in version 3/version 4 beta and don’t remember “services”. But by the same token, Laravel didn’t stop me from defining my own classes and calling them what I want.
But yeah, you’re absolutely right in that business logic that needs to be called in multiple contexts (controllers, console commands, queued jobs, etc) should be extracted so it can be used across them.