When comparing Dropwizard vs Bottle, the Slant community recommends Bottle for most people. In the question“What are the best backend web frameworks?” Bottle is ranked 17th while Dropwizard is ranked 26th. The most important reason people chose Bottle is:
Bottle works around the one-file approach, everything is done in a `bottle.py` file. This means that it's extremely easy to share and upload your application since it practically is just one python file.
Ranked in these QuestionsQuestion Ranking
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.
Pro Single-file distribution
Bottle works around the one-file approach, everything is done in a
bottle.py file. This means that it's extremely easy to share and upload your application since it practically is just one python file.
Being a small one file distribution it includes almost every vital thing you need to support little websites (routing, templating). Everything else can be implemented using plugins.
Pro No need to install
It is so little there's no need to install, it is included in the standard libs python.
Pro Async, *let friendly
Using it with gevent is a breeze. It's a WSGI app so it's easy to make it work with anything.
Pro Truly magnificent
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.
Con Small community. Difficult to find online docs and examples
Con Very hard to develop projects that are not smaller than 1000 lines
While Bottle is a great framework for building small applications (generally less than 1000 lines of code), it starts getting very hard to manage your application if you want to go even a bit larger than that.
The fact that it follows a single-file distribution model and that it's missing something like Flask's blueprints only make this problem worse.