CakePHP vs. Joomla! vs. Symfony

If you need to create simple CRUD applications using a MVC framework, I could say CakePHP could achieve this. But with frameworks like Laravel on the market, I would have a hard time recommending CakePHP for anything.

Incentivized

If your developers want to have some fun, Joomla offers the stability and friendliness to do custom coding. Certain marketing initiatives require us to get "cute" with the interface, and Joomla allows for that a bit easier than WordPress (and definitely easier than sites like Squarespace). The security of Joomla is also always a plus.

Incentivized

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

• Easy learning curve
• Can be used by new developers without paying a formation
• The MVC is pretty well implemented

Incentivized

• Security. Its got many new features in the new Joomla! 4 which make the already good security even better. I like the ability to use my Yubi keys to log in with the new webauth standard, I don't think any other CMS has that built in
• W3C Accessibility Guidelines (WCAG) 2.1 (with AA compliance)
• Really good SEO that gets our sites to the top of the search engines again without the need for any extra things
• Speed, it gets a really good score (100%) in the google lighthouse on our server, can't beat that

• 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

• The biggest issue inherit in CakePHP, and why we switched to Laravel, is the base configuration of the program. Most people aree that CakePHP uses old (outdated, even dangerous) PHP habits. There is some truth in this: Cake has not been as quick to adapt to the newer PHP versions as they should. I was always surprised that with new major releases, from 2.4 to 2.5 for example, that the minimum version of PHP will never increase. For example, CakePHP only requires version 5.2.8 of PHP, but it would not have been difficult to update the minimum version at least 5.3 when adapting a new version.
• Speed - our company had many issues scaling CakePHP to a medium size application software, even with using REDIS/memcache we would still run into many issues with the built-in ORM.

Incentivized

• Because Joomla's user community is smaller than WP, it lacks as many choices from 3rd party developers, meaning it can be a little more difficult to find the right extension for what you need to accomplish
• Along the same vein, most of the best 3rd-party software for Joomla! is paid
• Simple features such as Add to Menu and Cache cleaners should be adopted as part of the Joomla! core, though they are available as extensions
• Joomla! could use a simpler and easier URL rewriting process

Incentivized

• More powerful ecosystem of apps (paid and free)
• Doctrine (which is the goto ORM) needs more work
• Queue manager UI
• Deployment options

Incentivized

I gave it a rating of 10 because I just love how Joomla! works, how it is set up and how it handles many users. Also it is very fast, and there is no overload on the MySQL database or servers ever.

Incentivized

Joomla! 3.x is easily installed either manually or via a script provided by your host. It contains most of the tools needed to begin creating websites right from the start. Those features that it doesn't have are easily installed via links and buttons from the thousands of extensions available in the community

It can be a little complex at the begining comapred to some other frameworks, but this gives very good structure and makes it bulletproof for scaling actually large applications. The framework is built in a way that you can start simple and bring incremental improvements to make sure your app responds to traffic, demand, and growing usage.

Incentivized

Today's Modern Joomla performs very well and is robust and durable. The pages load faster than they ever did in the past and Modern Joomla's integration into other software or systems has become seamless. Modern Joomla sites will last long and will stay running forever.

Incentivized

Between the core Joomla developers who are excellent at answering questions and providing support, you have a whole community of developers who work with Joomla and are happy to help fellow developers out answering questions and supporting the Joomla project. Out of the many communities I am involved in for open-source software, Joomla's community is by far the best.

Incentivized

There is a lot of community support but because Symfony is so flexible and unopinionated, there are too many ways to do things and if you lock yourself into one way, most of the advice online will not work for you.

Incentivized

It is good if you know Joomla! if not it can get a bit confusing

Joomla has gone through tremendous growing pains. It is now better than ever. But before, when it was going from 1.5-2.5, the templates and plugins would break over and over again. If you don't understand what Joomla was trying to do back then, you might have a bad attitude toward it. Today, those pains are over and things don't break like they used to during that time period.

Incentivized

Cakephp is more easy to implement and to learn that CodeIgniter. That's why I switched pretty quickly from the first (CodeIgniter) to cakephp.

Incentivized

We tested other platforms like WordPress, Magento and some local CMS. 
But Joomla offered us better resources for generating content.
Joomla is a CMS suitable for many types of projects, especially if you have several people editing content at the same time. 
It allows you to maintain visual standardization and offers many options for working with images. 
With its ability to control access to different articles, categories or even different components, it is a great tool, even if they are managed by different people.

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

• Negative Impact - we ended up having to rewrite our entire web-application from CakePHP to Laravel.

Incentivized

• Joomla has reduced our costs of rolling out a new website because it uses less developer time and can be rolled out by individual users as needed.
• Joomla has a lot of extensions and add-ons that make it easy to create and implement advanced solutions quickly.

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