/explore
|
You are here 
|
richardmiller.co.uk | ||
| | | | |
www.beberlei.de
|
|
| | | | | ||
| | | | |
tomasvotruba.com
|
|
| | | | | In the previous post, we looked at [When Symfony Http Kernel is a Too Big Hammer to Use](/blog/when-symfony-http-kernel-is-too-big-hammer-to-use). We talked about the enormous content this package provides, but we don't need it. Today we'll have a little self-reflecting pause in the middle of the 4-post journey. We'll look at the main glue in Symfony Kernel - the Bundle. **Can we find a way to decompose it and use it without Kernel?** | |
| | | | |
williamdurand.fr
|
|
| | | | | After having described a decent folder structure and made things clear about DDD and this series, I will continue to bootstrap the sample application, focusing on a basic persistence layer and testing. It is not tied to DDD but it is worth writing about these two points. | |
| | | | |
tomasvotruba.com
|
|
| | | Another anti-pattern that deserves more attention than it has. I often see this in Symfony projects I consult and when I ask the dev *why* did he or she choose listener over subscriber, they don't really know - "it was in the Symfony documentation, you can read it there". Not good enough. **So why you should never use a listener?** | ||
