Symfony Reviews and Ratings

Use Cases and Deployment Scope

I have used Symfony a couple of times in the past both working on personal projects, as a freelance developer and at least a couple of times with different employers. Symfony is one of those PHP frameworks that at first had way too many things but with time, it started to become a simpler and more efficient framework to build simple to robust applications. In my personal experience, I used Symfony for projects which varied from small API's, console applications to robust web scalable systems. I had the chance to participate in projects where Symfony was used for lead generation projects, custom API's for mobile applications and small personal projects. The main reason why Symfony was used most of the times was the available documentation and the large community of developers supporting it.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

Symfony was the chosen framework to build the website. It was chosen primarily for the community support and opinionated structure that is suited for large projects from the beginning.

Likelihood to Recommend

If you need to use a Linux stack and you have something against Laravel, which I consider a simplified, optimized, and better documented version of Symfony, you should go with Symfony. But if you are inheriting a Symfony project, I would just try to upgrade it to the latest Symfony rather than switch to Laravel. Symfony can be very confusing to junior developers and its flexibility results in them writing bad code if they don't invest time into reading the whole documentation and studying the best practice examples.

Use Cases and Deployment Scope

We use Symfony in our department for the backend of our applications. In the past, we used it for some microservices as well, but switched to a more performant language, as PHP was holding us back.

Likelihood to Recommend

Symfony is well suited for developing anywhere from simple to complex backends for web applications. I would even say it is suitable for developing APIs and services if you need to stay in the PHP realm. I see no major drawbacks to Symfony aside from the limitations of its core PHP language, not the framework itself.

Use Cases and Deployment Scope

The Symfony framework underpins several of the applications that we use. Most notably, is it used by Drupal 8 core, and so it makes its way into many of our client projects. We have also used components of Symfony directly in other PHP web applications, as we find that it puts a lot of industry-standard practices in place saving us time and headaches. It's easy to use and always getting better.

Likelihood to Recommend

If someone is writing a PHP application and looking to determine which framework would be best suited, I think Symfony is almost always a great choice. I sometimes prefer to use other frameworks or tools that were built with Symfony, such as Laravel or Drupal 8, but unless you need more than what Symfony offers, then using Symfony directly is simple and powerful.

Use Cases and Deployment Scope

We use Symfony PHP framework for the development of the majority of the projects within the company. Some of the projects use Symfony for the front-end (for example, <a href="http://www.grossum.com">www.grossum.com</a>) as well as the back-end. Symfony as a back-end is used for most of the mobile apps as well as the web. From all the research our developers have done and their experience, Symfony is one of the most convenient frameworks for complex projects.

Likelihood to Recommend

Symfony is good for ensuring scalability of the project (granted, you also would require a cloud for that, but that's another topic), therefore it is a good framework to use if you are thinking about creating an enterprise product. Symfony's documentation is also done quite well, so that's another advantage because you can easily trace the changes and find out what happened when.

Symfony isn't the ideal choice for a small-scale website simply because there are other frameworks and CMS that would do that quicker and easier. If you, however, need strong backend for a project, Symfony's your mate.

Use Cases and Deployment Scope

Symfony is our main development framework, its stack or base components make up 100% of our products. We have built not just products purchased by other companies but also platforms for our internal consumption and company management. Accounting, Reporting, E-Commerce, Blogs and Bots are just a few of the areas where we have been using Symfony. Using Symfony allows us to speed up the development process and know for sure that it is strongly supported by its robust community.

Likelihood to Recommend

Symfony is a strong framework because of its strong set of components. Its architecture allows Symfony to grow and allows us to use what we need. It is well suited for both small bots, console commands, micro services and big monoliths.