I use repositories for keeping my business logic separated from the data access logic and mostly follow bosnadev .
I then use services to keep more complex code out of my controllers or to implement third party libraries.
As for using services inside services, I don't really see any problems with that
As @LaurentMeganck said there shouldn't be a problem with a class using multiple services.
You can easily encapsulate multiple units of work behind a single service call if you want.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community