Laravel is a free, open source web application PHP framework.
N/A
Symfony
Score 10.0 out of 10
N/A
Symfony is a PHP framework from French company SensioLabs.
N/A
Pricing
Laravel PHP Framework
Symfony
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Laravel PHP Framework
Symfony
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Laravel PHP Framework
Symfony
Considered Both Products
Laravel PHP Framework
Verified User
Team Lead
Chose Laravel PHP Framework
The best comparison I can make is against Symfony. It's curious that Laravel is built on top of Symfony. They chose the packages that they found to be useful. Symfony for instance comes with way too much stuff that in the end you never use, and Laravel just comes with the right …
Laravel is built on top of Symfony so is naturally a better upgrade. It is far superior than cake and igniter (in my opinion). I don't remember, but somewhere in internet someone made a comparison with Laravel and others as racing motor-bike vs a cycle. Because of large …
Originally, it was a decision between Zend, CodeIgniter, and CakePHP for me. I chose CakePHP and used it as my main PHP framework for at least a couple of years before noticing and giving Laravel a fair try. Ultimately I selected Laravel because I felt it fit with my preferred …
I inherited Laravel projects originally created by other developers. I haven't migrated clients at this time, however as the project gets bigger and I need to find more elaborate workarounds to address needs that option will be put on the table.
I would say Laravel is by far Symfony's greatest rival. Laravel was actually a PHP framework that appears from Symfony, using only the packages that it really required. After some years, both projects have grown apart significantly, but you can still see Laravel using some of …
Symfony has become such a standard that many frameworks which previously may have been seen as competition, are actually adopting Symfony components to allow them to focus more on what makes their solution unique. Drupal 8 has replaced much of its low-level internal code with …
We've compared Symfony to Laravel, Zend, Drupal, and Silex (as well as to pure PHP) and it was so far the most convenient tool for enterprise scalable products. Among all compared, Laravel was next in line in terms of the convenience and ease. Drupal used to be popular, but now …
Symfony is strengthened by its amazing set of components. It is more flexible and strong, now with the introduction of flex on Symfony 4.x it's even more flexible and adapting for the future. Its architecture is robust and allows developers to focus on products. Symfony has …
Laravel is ideally suited for fluent PHP developers who want a framework that can be used to both rapidly prototype web applications as well as support scalable, enterprise-level solutions. I think where it is less ideal is where the client has an expectation of using a certain CMS, or of having a certain experience on the admin side that would perhaps be better suited to a full CMS such as Drupal or WordPress. Additionally, for developers who don't want to write PHP code, Laravel may not be the best solution.
Any small project which you want to have ready in a couple of hours would be probably a bad candidate for using Symfony. Even the most seasoned senior developer can easily spend hours or days creating a small MVP with Symfony. While Symfony's learning curve isn't necessarily bad and will depend a lot on the architectural knowledge of the developer itself, because of the modularity required by Symfony you will need to spend a significant amount of time coding. If you are looking for a quick project, perhaps this framework isn't the best solution. Robust applications can benefit from Symfony's architecture. I have participated in projects on different industries including lead generation, marketing and even some micro-services for other industries which use Symfony. Because of how thorough the framework has been architected, you will have a reliable solution.
Sonata Admin for Symfony is very versatile and we've used it for both the admin part of our website (even created a landing page constructor using it) and for the ERP system we've developed for inside use.
It is easy to learn if you know PHP and the community is quite large so you can easily find experts to help you with issues.
It's good for high-load projects. We have used it for the back-end of a custom affiliate marketing system that currently processes over 180 million requests per day.
Significant learning curve. You cannot be an expert in a week. It takes many experimentations to properly understand the underlying concept. We ourselves learned it by using it on the job.
Too much to soak in. Laravel is in everything. Any part of backend development you wish to do, Laravel has a way to do that. It is great, but also overwhelming at the same time.
Vendor lock in. Once you are in Laravel, it would not be easy to switch to something else.
Laracasts (their online video tutorials) are paid :( I understand the logic behind it, but I secretly wish it would be free.
The eloquent ORM is not my recommendation. Let's say you want to write a join, and based on the result you wish to create two objects. If you use Laravel to do automatic joins for you, Laravel internally actually makes two calls to database and creates your two object rather than making one join call and figuring out the results. This makes your queries slow. For this reason, I use everything except eloquent from Laravel. I rather write my own native queries and control the creation of objects then rely on Laravel to do it. But I am sure with time Laravel will make fewer calls to DB.
Symfony has a great following and finding relevant articles or looking into social channels for support is quite easy. I have no comments on any type of official support because I didn't ever need to look into it.
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.
Symfony has become such a standard that many frameworks which previously may have been seen as competition, are actually adopting Symfony components to allow them to focus more on what makes their solution unique. Drupal 8 has replaced much of its low-level internal code with Symfony components. Laravel utilizes much from Symfony and builds on it. CakePHP was my preferred framework over Zend and CodeIgniter, but now I typically prefer Symfony or Laravel depending on the type of application and complexity of what I'm doing.
Laravel allows us to rapidly prototype and build complete, scalable applications internally, which saves us time and allows us to have internal tools that fit out precise needs. We use Symfony for a similar purpose, but Laravel is an even higher-level framework that we find saves us substantially more time when building many types of web applications.
Laravel solves many of the underlying concerns of building a large application (such as authentication, authorization, secure input handling) in the right ways. It saves us from handling those low-level concerns ourselves, potentially in a way that could take a lot of time or sets us up for issues in the future. It's tough to assign an ROI to this, but I'm sure it has prevented issues and saved time, which both have an impact on our financial situation.
One negative thing to point out of Symfony is how painful it is to migrate legacy or relatively old projects from previous versions of Symfony into newer versions.
Symfony projects are usually reliable and provide the results you need.
Performance can be an issue sometime depending on the kind of project you are working on. Symfony can have some issues with cache.
