CakePHP vs. Laravel PHP Framework

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CakePHP
Score 1.7 out of 10
N/A
CakePHP is a free and open source PHP framework.N/A
Laravel PHP Framework
Score 8.6 out of 10
N/A
Laravel is a free, open source web application PHP framework.N/A
Pricing
CakePHPLaravel PHP Framework
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CakePHPLaravel PHP Framework
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CakePHPLaravel PHP Framework
Best Alternatives
CakePHPLaravel PHP Framework
Small Businesses
Laravel PHP Framework
Laravel PHP Framework
Score 8.6 out of 10
CodeIgniter
CodeIgniter
Score 10.0 out of 10
Medium-sized Companies
Laravel PHP Framework
Laravel PHP Framework
Score 8.6 out of 10
Symfony
Symfony
Score 10.0 out of 10
Enterprises

No answers on this topic

No answers on this topic

All AlternativesView all alternativesView all alternatives
User Ratings
CakePHPLaravel PHP Framework
Likelihood to Recommend
5.0
(0 ratings)
7.7
(0 ratings)
Likelihood to Renew
-
(0 ratings)
8.0
(0 ratings)
User Testimonials
CakePHPLaravel PHP Framework
Likelihood to Recommend
CakePhp is useful if you need to implement a code with different modules (users, payments, pictures). CakePhp is useless if you need to build a quick project that requires a few lines of codes, it's faster to reuse and adapt code from old projects.
Read full review
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.
Read full review
Pros
  • Easy learning curve
  • Can be used by new developers without paying a formation
  • The MVC is pretty well implemented
Read full review
  • 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)
Read full review
Cons
  • 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.
Read full review
  • 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.
Read full review
Alternatives Considered
We didn't know any better - if we had, we would have not chosen CakePHP.
Read full review
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.
Read full review
Return on Investment
  • Negative Impact - we ended up having to rewrite our entire web-application from CakePHP to Laravel.
Read full review
  • 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.
Read full review
ScreenShots