Dropwizard vs CakePHP

The application can be run and debugged from the IDE without the need to recompile or redeploy the WAR file. This is because a Dropwizard web application creates on main program which starts the jetty container.

Dropwizard comes with application metrics integrated out of the box. These metrics provide a lot of useful information such as request/response time.

For example, to get the execution time of a method, the @Timed annotation is used.

Starting a project with Dropwizard si very easy and bootstraping is quick and painless. All that's needed is a single dependency added in the pom.xml file and it's ready to go.

Cake has a built-in ORM which is pretty easy to use and learn. Building queries can also be done very easily and fetching entire columns can be done in one or two lines of code.

Developing in CakePHP is very fast and flexible.

CakePHP is about fast and reliable development, it achieves this by following the convention over configuration principle as it's heavily inspired by Rails (which follows the same programming paradigm).

Convention over configuration is all about making it easier for the developer to start immediately writing code without worrying on what's going on "under the hood".

CakePHP has a large library of helper classes with features such as:

• Authorization
• AJAX
• Forms
• E-mails
• Internationalization
  etc...

Cake's great community has thrown together an exhaustive and amazing list of resources to get started with CakePHP. It's open source and can be found on GitHub.

CakePHP open source and is licensed under the MIT license.