Site-service architecture is a name we have given to our newest way of organizing code. The concept here is to break up the app into services. Each service should contain all of its own needs such as models, controllers, routes, events, etc. The service will end up looking like a miniature app or a small package in the end, and this is what we are wanting to see. The benefits of this are that all the code you need for the service is inside a single directory and easy to find.
To begin with services, create a Services folder in your app directory if one doesn’t exist already. Inside that folder
you should place any of the following folders you may need.
📁 Commands
📁 Contracts
📁 Events
📁 Http
📁 Controllers
📁 Routes
📁 Jobs
📁 Listeners
📁 Managers
📁 Models
📁 Repositories
📁 Traits
📁 Transformers
Events, Http, Http/Controllers, Listeners and Models all behave exactly the same as their app level counterparts. Commands
is where you would place any commands. These are the special jobs we have that are fired and forgotten about using
the command() helper. Contracts would be where you place all of your interface files. Http/Routes is the location for
your class based routes. Repositories would be where repositories go should you need them. Transformers is the location
of the transformer files used to make sure the view and vue files have consistent data at all times. These could also be
used for APIs. Managers are classes that handle a specific task. Things like handling checkout by combining all the items
and storing in the database. It creates a single class that the entire app should use to handle the task.
You can find our naming convention on micro services in the code style guide.