When comparing Firebase vs Dropwizard, the Slant community recommends Dropwizard for most people. In the question“What are the best backend web frameworks?” Dropwizard is ranked 28th while Firebase is ranked 31st. The most important reason people chose Dropwizard is:
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.
Ranked in these QuestionsQuestion Ranking
Pros
Pro One command deploys and rollbacks
The content is deployed immediately through the Firebase CLI. Once it's uploaded, the content is served immediately. If you have made a mistake, you don't need to re-upload a new version, through the Admin dashboard you can easily rollback to a previous version.
Pro Assured future support
Google acquired Firebase in Oct. 2014. This gives Firebase a degree of trustworthiness in their service and future support since they are backed by such a large company.
Pro Well documented
The documentation and quick start guides are informative and easy to learn.
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 Hosted
Firebase locks you in to Google's service; you can't run it on your own servers.
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.