Laravel for Clients: why Laravel and not Symfony?

Notice: This is one chapter of my e-book “Laravel for Clients” – it’s available for free at LaravelForClients.com

In this chapter of my e-book let’s take on the “holy war” between frameworks. I’m not kidding here – developers actually fight (verbally only, I hope) with each other about what framework to use.

So, in general, there’s not much difference, actually. It’s a matter of how well a particular person is familiar with a certain framework – so a person who has created 10 projects with Laravel would probably deliver faster and with more quality than a developer with 1-2 projects experience with Symfony framework.

There is some classification in the frameworks world – there are “full” frameworks (mentioned above) and smaller so-called “micro-frameworks” – examples are Lumen (“stripped” Laravel version), Slim, Silex, Flight. So except for those micro-frameworks, any up-to-date modern framework can do the job.

Speaking of “up-to-date”, this is probably the most important argument in this question. Since you’re probably creating a project with plans to update and maintain it in the future, you need a framework with a big enough future and strong community to support it. So currently on the PHP market there are two strong leaders from that perspective: Laravel and Symfony. All the others are less popular, for different reasons – some abandoned by their creators (CodeIgniter), some are too complicated (Zend Framework), some have too small communities (Yii, Cake PHP).

Now, how to choose between market leaders – Laravel vs Symfony? Both are really good and I can recommend both. The main difference between them is strictness of the code structure. Symfony is much more strict in the way how the code is written, therefore more popular in enterprise-like applications, and Laravel allows more “freedom” to developers and therefore is more popular in smaller web-apps with lower entry to dev-market.

Also, for those same reasons Symfony developers tend to be more expensive – simply put, there are less Symfony professionals in comparison to Laravel.

But whichever you choose for your project – it’s more about finding the right developer in that framework space, than framework choice itself.

– – – – – –

Want to read the full e-book for free? Go to LaravelForClients.com

Like our articles?
Check out our Laravel online courses!

5 COMMENTS

  1. you are right in some of your article and not right in others
    laravel and symfony is already popular but codeigniter is not abandoned by their creators as you said
    codeigniter 4 is will came with strong features and will be built in php 7 completely
    and i think it will be the master of php community

    • Hi, thanks for the reply. I’m afraid it’s too late to get back the old CodeIgniter fans, been one of them myself before switching to Laravel.
      Unless, as you’re saying, version 4 will be a completely new thing (then you can also change the name of the framework probably) and will build a new army of fans. But it failed for new versions from Yii and Zend, why should it succeed for Codeigniter?

  2. Hey,
    Great job on here, About the actual discussion, Laravel is built with Symfony. Plus though Laravel runs faster when Symfony is caching source code, the average loading time for web sites on Laravel is reported to be about 60 milliseconds, while for ones on Symfony about 250.

  3. Read your full post.
    It seems that you have covered all major points.

    It is true that decision of choosing framework depends on functionality not on features.
    According to GithHub, Laravel is very popular framework. More than 30 000 developers from all over the world exceedingly acknowledge robust features of Laravel.
    Selecting the right framework for your project saves the time and cost also.

    Thanks for sharing such a detailed Article.

LEAVE A REPLY

Please enter your comment!
Please enter your name here