When comparing Dropwizard vs Adonisjs, the Slant community recommends Adonisjs for most people. In the question“What are the best web frameworks to create a web REST API?” Adonisjs is ranked 14th while Dropwizard is ranked 26th. The most important reason people chose Adonisjs is:
If you are already programming in PHP with Laravel, you will have no trouble starting development with Node using Adonis.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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 Based on Laravel PHP Framework
If you are already programming in PHP with Laravel, you will have no trouble starting development with Node using Adonis.
Pro Similar to Rails
Pro Built-in modules for everything
There are built-in modules for everything: Auth, Social Auth, mailing ect
Pro Has websocket support out of the box
Pro Very good documentation
Pro Easy to learn, especially if you're already familiar with Laravel
Pro Option for full-stack or api standalone implementation
You can choose to use the full-stack version or if you wish to build a RESTful API you can choose to use the api standalone version.
Cons
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 No NOSQL integration
Only used ORM, not ODM.
