Design Pattern : Service Layer with Laravel 5
François Louchart
19211

While there is no standard answer about how many Service classes you should create, is it per action or per CRUD, I believe this should be more of a how you want to package your app, keeping file size in mind.

For example, in my “UserService” I have 4 methods that are not very long/complex, after separating DB logic into repositories. I mind to keep them together in single unit.

Where as in my news “NewsService”, I have 5 methods but are very complex in nature. I have separated them into two different classes. One for Create/Edit and other to Query.