CakePHP has always had a fast and consistent development and, with that goal, CakePHP places a great emphasis on convention. Therefore, like Ruby on Rails (of which CakePHP drew much of its inspiration), CakePHP strongly adheres to the convention on the configuration principle.
CakePHP, on the other hand, has always been largely compatible with previous versions. In fact, every release since version 2.0 has been 100% compatible with previous versions, which means that an update takes several seconds.
Conventions mean that a developer does not have to think about "where things are going" when he learns how to use the CakePHP framework, since the default values for these rules are already established. While one needs to become familiar with the CakePHP conventions, once mastered, the developer can concentrate on core development, instead of having to worry about where the code is placed and other configuration issues.
Other advantages would be:
1. Excellent for the application (not only on a medium scale but on a large scale, already used in our company)
2. Many magical methods that greatly reduce writing time and are very useful
3. Maintenance of appearance, a new programmer can easily understand the code
5. It is safe and covers common security
Its biggest problem is the configuration because it presents many difficulties at the time of making it.
It can be argued that CakePHP is an inherited framework, or uses old (bad) 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. Anyone in an existing version 5.2 of PHP could have continued to use the existing branch of version 2.x. As they released new major versions, they could have increased the PHP version and made changes accordingly (keeping the revolution going).
Everyone has a different opinion about the best framework, and my advice to any developer is to not judge a book by its cover and try it as many times as possible to find what you really like. Ask a classroom what is the best taste of ice cream, and I'm sure there will be several different answers. The frames are not different! My opinion is to recommend it
CakePHP is really the best php framework. We use it mainly to build a business application and ideal with many subsystems urilizados in the company. It is very robust, has a clean MVC architecture, powerful command line tools. Ideal if you have platforms that should be robust