Dropwizard vs Beego

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.

Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.

Beego has a built-in tool which watches the code for changes. This tool (called bee tool) can be configured to run any task once the code changes. It can run tests or reload and rebuild the whole project.

Beego's eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. Beego examples and documentation all use the beego ORM. No need to learn to use and integrate another ORMs API.