When comparing Pyramid vs Dropwizard, the Slant community recommends Pyramid for most people. In the question“What are the best backend web frameworks?” Pyramid is ranked 15th while Dropwizard is ranked 28th. The most important reason people chose Pyramid is:
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very flexible
Pyramid can be used for creating small applications quickly and easily, but it also powers up large enterprise-scale applications such as Dropbox.
Pro Persistence agnostic
Either NoSQL and SQL (including SQLAlchemy plugin).
Pro Comes with security included
Includes authorization and authentication with multiple backends.
Pro Enhanced productivity and less timewasting
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.

Pro Application metrics integrated into the framework
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.

Pro Quick project bootstrap
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.
Cons
Con The great number of options it offers can become intimidating
One of Pyramid's greatest drawbacks is that it requires a lot of set up in the beginning of a project. This can feel overwhelming and can keep people away from using it.
Con Does not allow a lot a freedom of choice
Dropwizard removes a lot of freedom that the developer may have with other frameworks because of the fact that it tries to do everything itself. It chooses the best Java libraries for the job required, without allowing the developer much choice.
