Silex is a microframework meant to be used in small projects. It's suitable for small websites with low traffic. It is also a good way to introduce yourself into some concepts like dependency injection, without introducing too many abstraction layers. They've recently introduced the target in their website as "single-file apps", giving you a bit of the target scope for the framework.

I think it should be fairly accepted fact that Silex is not suitable for anything big. Silex will not perform badly if your project works, but it will not be the nicest to work with once you start growing, as it will not help you too much. Symfony uses concepts you'll see in Silex and is a full stack framework you can use for bigger applications with lots of bundles, plugins and a big community there to help you.

All in all, it wouldn't be my first choice for a framework, once you get comfortable with bigger frameworks there's usually no need to limit yourself by using a small one.

Silex is a microframework meant to be used in small projects. It's suitable for small websites with low traffic. It is also a good way to introduce yourself into some concepts like dependency injection, without introducing too many abstraction layers. They've recently introduced the target in their website as "single-file apps", giving you a bit of the target scope for the framework.

I think it should be fairly accepted fact that Silex is not suitable for anything big. Silex will not perform badly if your project works, but it will not be the nicest to work with once you start growing, as it will not help you too much. Symfony uses concepts you'll see in Silex and is a full stack framework you can use for bigger applications with lots of bundles, plugins and a big community there to help you.

Edit:

Note I cannot delete the answer as it has been accepted. I haven't used PHP in years now, since then, Silex has changed their approach from "microframework" to being just a library it seems. Whatever the case, the down-voting I believe must come from people involved with the project, probably upset of having created something which didn't take off as they may have hoped.

Just read the product docs, this was a request for an opinion which was given and accepted. I don't think this question belongs to stackoverflow anyway.

It is a matter of opinion, but I am of the opinion that Silex is not really suitable for anything, there's really no advantages in using that over Symfony, you lose so much and you gain nothing. My guess is it was built as a door into Symfony which looks less scary for people who haven't tried it, but Symfony is really not hard to use. Symfony does not add overhead, it comes with some features available if you want to configure them in, but you don't have to. It's built under the inversion of control philosophy and you truly just need to write PHP and then use the framework to wire your classes up and set up the access point (HTTP in your case).

Though I think it should be fairly accepted fact that Silex is not suitable for anything big. Silex will not perform badly if your project works, but it will not be the nicest to work with, and it doesn't help you too much.

All in all, when I want to write a REST webservice PHP is definitely not my first choice, but if you must, I think Symfony is the way to go.

Silex is a microframework meant to be used in small projects. It's suitable for small websites with low traffic. It is also a good way to introduce yourself into some concepts like dependency injection, without introducing too many abstraction layers. They've recently introduced the target in their website as "single-file apps", giving you a bit of the target scope for the framework.

I think it should be fairly accepted fact that Silex is not suitable for anything big. Silex will not perform badly if your project works, but it will not be the nicest to work with once you start growing, as it will not help you too much. Symfony uses concepts you'll see in Silex and is a full stack framework you can use for bigger applications with lots of bundles, plugins and a big community there to help you.

All in all, it wouldn't be my first choice for a framework, once you get comfortable with bigger frameworks there's usually no need to limit yourself by using a small one.