Laravel PHP Framework vs. Liferay Digital Experience Platform (DXP)

This framework's pros are more than cons. It can be used for many purposes; building e-commerce is one of them.

1. Code is clean and simple because of its routing.

2. Connection to database and query optimizing.

3. The amazing automatic memory to remember past queries is a big plus.

4. Migrations is the most crucial feature of this framework.

5. Supporting unit tests out of the box.

6. Artisan to use command line.

7. Large community to support your queries.

Incentivized

Lifeary Digital Experience Platform(DXP) is well suited for long meeting, personalisation of data , customer data and customer management in any circumstances. The things in here that are less appropriate are that the picturiastion will be much better. Have individual databases for individual programs and the list of client should be listed systematically.

Incentivized

• Many libraries available which simplify integration of SaaS APIs within your application (eg, MailChimp, Mandrill, Stripe, Authorize.net)
• Pre-packaged tools to facilitate common tasks when building applications (eg, User Authentication and Authorization, Background Jobs, Queues, etc)
• Support for a broad set of technologies out of the box (eg, PostgreSQL, MySQL/MariaDB, MemcacheD, BeanstalkD, Redis, etc)

Incentivized

• User management
• Security and access management
• WYSIWYG

• There isn't a whole lot to dislike about the framework, honestly. If I am forced to say something is that sometimes the authors change the directory layout and it's not always easy to deal with. That being said, I've never not been able to upgrade within a few hours.
• Sometimes using the artisan CLI - it requires additional tweaking to get it running on non-standard application rollouts.

Incentivized

• It requires technical expertise and the right people to achieve customization.
• There is little documentation available for certain functions that make them a bit complex to master.
• The SSL function for login.

Incentivized

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

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 development style, it utilized many of the modern best-practices I wanted to follow, and I felt that it allowed me to build better things in less time that seemed more maintainable. I have used, and still do use, Symfony directly for certain things, but I think of it (and use it) more as a code library than as a full application framework. When I'm building a web application, I tend to prefer Laravel.

Incentivized

Alfresco: Very good CMS but not good for presentation or front end technology. Portofino: Not much scalable and high available CMS. eXo Platform: Slowly growing in market but not mature community like Liferay and less support from community. Microsoft SharePoint: Proprietary Software from Microsoft. Nuxeo ECM Platform: Picking up the market but not mature community and support from the community.

• Positive: Our delivery time for PHP application is faster than usual.
• Positive: Developers are happy and they write better code with their usual development tools. No tool-upgrade necessary.
• Negative: Initial delivery took 6 months extra and had to rewrite project several times.

Incentivized

• Can reduce IT costs eventually.
• Increases upfront costs due to technical knowledge needed for initial setup and maintenance.
• Hard to analyze ROI until after it's totally implemented.

Incentivized