What is the correct structure for a large Laravel 5 project?

Question

Laravel

Hello!
Who designed large projects on Laravel5? I'm interested in your vision on code organization, folder structure, etc.
For example, where to store traits or interfaces? Not all the same tuly in the model, right? I would like the code to be structured and the classes to be compact. In general, what is your vision for this?

Answer 1

store traits or interfaces

tuly in the model

Most here thought:
"Ahh! Fuck my legs! You just blew my brain!!! Go away, Demon, go to your future or past (or where did you come from) !!!"
In general: Laravel is NOT recommended for large projects. has a large redundancy in the used library classes and, as a result, a strong drop in the execution speed and excessive requirements for the hardware component.
It is always better to write large projects in pure native, optimizing the project architecture in advance for the required functional requirements with a given strength.

Answer 2

What's wrong with the real structure? It is quite suitable for "large" applications.
If something is missing, then we create our own folders and do not forget to write in composer.json