Symfony2 bundles: am I using them right?

Question

I have an application which is developed in Symfony2. Now the structure for it is as follows:

• FrontBundle - includes everything rela

Answer 1

Like Elnur said, use one AppBundle is a good practice.

A single bundle implements the MVC pattern himself so i think it's not a good idea to use bundles to separate your layers.

I think the best way to use bundles is to think "open source". If the feature you are developping is enough generic to be released for everyone, or to be reused in a future project, place this feature in a bundle. This way will force you to build the feature without any business rule which belong in your AppBundle.

Bundles are bricks

Answer 2

There are no hard and fast rules on how to structure your app using bundles, but here's what I came to after developing on Symfony2 for close to a year.

Use one app specific bundle. At first, I started with multiple bundles like CommonBundle, UserBundle, MainBundle, BlogBundle, ContactBundle, etc. That proved to be not so convenient in the end, so I switched to just one app specific bundle — AppBundle.

You can organize your code neatly using subnamespaces. For example, the backend controllers would go to the AppBundle\Controller\Backend subnamespace.

Note that I'm talking about one app specific bundle — that stuff that's unique to the concrete app and won't make sense to reuse elsewhere. You can still develop separate bundles for reusable stuff and put them into the vendors infrastructure.

Keep non Symfony specific stuff out of bundles. There is no need to have a bundle for the model and the Service Layer classes in a bundle if they are not Symfony2 specific. See this question and my answer for further details.

Answer 3

There are different ways to organise application structure for your projects. But if you want to distribute your bundles and follow symfony best practices, then bundles are more features than separation of UI. More about bundles read in documentation.

I have two projects with the following structures, both valid I think:

1. making a bundle for each feature: BlogBundle, StoreBundle and so on, and AppBundle that contains general stuff. No Backend/Frontend separation. It's SaaS where backend is frontend in most cases.
2. One bundle for frontend, one for backend. They share only entities and domain specific stuff. The application has two different ends.