Liferay Digital Experience Platform (DXP) vs. Symfony

Liferay Portal is a framework which comes with a fine grained security/permission model, (Web) Content Management, Authentication and Authorization, outbox portlets with different features to manage content or users. So if any business application has below questions then I can recommend not to use Liferay as a platform.

• Application is big but not content or user driven.
• Application with few static contents.
• Application with batch transactions(DB) i.e. insert , update db records in batch.
• Application with ERP capabilities.
• Application with Big Data support.

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.

Incentivized

• Personalization
• Business to client relationship
• Customer management is better.

Incentivized

• 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.

Incentivized

• Harder to get started
• Enterprise level of options can cause confusion
• Development documentation could be better

Incentivized

• There are so many ways to do things that FAQs around the internet may not work for the way you did it.
• The default database ORM doctrine is not well documented and has a large learning curve when optimizing for high traffic.
• Matching the Symfony version with your selection of bundles makes it difficult to upgrade bundles because many things change between updates.

Incentivized

We are currently using Liferay Portal and plan to keep using it.

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.

Incentivized

Incentivized

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.

Incentivized

• Create a good environment
• Resolution is not so much better.
• Have a long things to do.
• Content management is better off.

Incentivized

• 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.

Incentivized