There was a small discussion on app structure in the old forum with interesting points of view : https://laracasts.com/forum/?p=2267-what-is-the-most-appropriate-way-to-structure-the-domain-level-
Laravel 5 App Structure for large applications
I am working on a fairly large Laravel application and wanted to get some input on the ideal namespace/directory structure, or at least a general sense of the advantages and disadvantages of different approaches.
I have been toying with two since the announcement of Laravel 4.3:
A) Pros/cons of organizing your app in terms of features? (Acme\Users) Which would have Acme\Users\Commands, Acme\Users\Repositories\, Acme\Users\Events, etc.
B) Or is it better to organize in terms of function? Acme\Commands\Users, Acme\Repositories\Users, Acme\Events\Users, etc.
Also, with option A, let's say you had a one to one relationship with a contact table. Would you group Contact model within the Acme\Users namespace or should it be divided up by resource, e.g. Acme\Contacts instead?
Thanks in advance.
Please or to participate in this conversation.