Which laravel project structure to choose?

Question

Laravel

I learned for myself that it is possible to create a project structure in modules with separate controllers, routes, models, etc. And I'm wondering how you feel about such a decision and do you think it's a waste of time? Also, what are the alternatives to this approach?
Example

Answer 1

Sometimes this is justified, sometimes not, it depends on the project.
At least - try it, you won't lose anything)) at the same time you will get a visual experience of creating service providers :)

Answer 2

IMHO a bike
for large projects lavarel is a pure backend
laravel is first of all programming by agreements - learn how to do it right first and then suffer nonsense

Answer 3

Start using the normal phpstrorm IDE and git instead of posting your project with vs on the mail cloud. And then, as in a fable - And you, friends, no matter how you sit down, You are not good at musicians.
A normal IDE will allow you to move from one structure to another through refactoring in an hour or two.