If you've used Silex before, you probably know it quickly becomes the little
engine that could. You start off with one file and a handful of routes, before
you know it, your application is a success and you've got dozens of routes, just
as many services, as well as a fair few middlewares, event listeners and error
handlers.

Silex is more of a library than a framework, it simply ties together a http
abstraction and a routing system, on top of a tiny little dependency injection
container. It doesn't prescribe any particular directory structure or make any
kind of decisions for you. When your Silex app grows, maybe it's about time you
made a few decisions.

In this talk we'll run through a really quick introduction to Silex, before
discussing some organised approaches to managing the growth of your Silex
application. There is no "one true method" for organising a Silex application,
hopefully after this talk you'll have enough options to carve out your own
method.