title: What will be the best practice of code separating for a large projects in Symfony4?
body: <p>The release of the popular framework's 4th version was marked by a capital changes in the structure for projects. Including the official documentation notes the following regarding the code bundling (<a href="http://symfony.com/doc/current/bundles.html" rel="noreferrer">http://symfony.com/doc/current/bundles.html</a>):</p>
  
  <blockquote>
    <p>In Symfony versions prior to 4.0, it was recommended to organize your own application code using bundles. This is no longer recommended and bundles should only be used to share code and features between multiple applications.</p>
  </blockquote>
  
  <p>In the 2nd and 3rd versions, the bundle performed two main tasks. 1) If the developer or a group of developers in their different projects used one large repetitive functional, then it could be taken out in a separate bundle and transferred from the project to the project. A good example of such use is a system of users in any project. It includes the models of User, Role, Permission (and possibly others), controllers for entity, plus controllers for signing in the app, signing out the app (the security policy may be different at the same time), and templates for view. Another good example is the administrative panel, the foundation for which is identical. 2) Symfony took separate functionality in different directories from the logic point of view and, accordingly, namespaces by bundling.
  For example, on one of my past projects, I divided the spaces: user management system, application gamification (social network goal), partner space, geo-environment (for working with maps and defining cities by IP), an environment for payment transactions. As follows.
  <a href="https://i.stack.imgur.com/pg7kj.png" rel="noreferrer"><img src="https://i.stack.imgur.com/pg7kj.png" alt="Symfony[2-3] project structure"></a></p>
  
  <p>In my next project I do not want to use anything other than Symfony4 to follow the best practices of the framework during the implementation of its new features.
  How can I organize the separation of logically independent code in different areas, if the official documentation no longer insists on the creation of bundles??? If all the classes of the model are stored in the same directory, this creates confusion and increases the time to find the desired file in the structure of a large project. The same applies to templates and indeed everything else. When I work with one functional, I have only dropdowned directories of this functionality.</p>
  
  <p>Is it now that Symfony encourages you to define the structure of classes, templates and the like at your own discretion?</p>