Level 2
Yes I think it is. I generally create a "Service" folder/namespace for any services/api I need to integrate with outside my application. So yes good approach. There shouldn't be any performance issue this is an architectural decision.
Jan 16, 2019
3
Level 3
Service Layer in laravel
Is it good idea to have a service layer in the application which holds the business logic, so that the controller work is to get the user data and return the response from services? I am using Laravel Passport for authentication and my client (app) is in different domain.
I have already gone through 3 pages of google and posting this question. Whats the impact of service layer on the performance of application? We have AWS setup for hosting. Any suggestions would be appreciated.
Level 122
passing some work to a service provider or your models to cut bloating your controllers is a good idea and will make practically no difference from a performance perspective.
1 like
Level 3
Please or to participate in this conversation.