eZ Platform vs. Laravel PHP Framework

For a new site: 1. Are there any hosting requirements? eZ Publish works best on a traditional LAMP stack. 2. What is the expertise of the development and systems administrations individuals? There should be some PHP development experience and a solid level of Apache and MySQL hosting. 3. Who will be managing the content of the site? What is their bandwidth for training? For ongoing content changes?

Incentivized

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

• Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
• Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
• Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.

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

• The template language: Outputting content or doing something special with it requires use of the templating language. Myself along with other developers I have trained, found this to be one of the biggest hurdles.
• Layout of physical files: The system decides what settings files and templates to use based on a hierarchy of modules. The same file can exist in multiple modules and you can find yourself deep within very similar looking folder structures, causing confusion during debugging.
• Community: eZ has a solid set of community contributors but the gap between it and Drupal or Wordpress is pretty large.

Incentivized

• 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

eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:

• Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
• End-user training is very straight-forward.
• Vendor support is available.
• Client IT departments can access if need (developers/designers/sysadmins).
• The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.

Incentivized

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

• Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
• Training: Due to its content taxonomy, end-user training often went well.
• Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.

Incentivized

• 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