Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariDropwizard vs N2O
When comparing Dropwizard vs N2O, the Slant community recommends Dropwizard for most people. In the question“What are the best backend web frameworks?” Dropwizard is ranked 28th while N2O is ranked 29th. 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.
Specs
Question 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 Fast binary data
Pro Binary encoding and protocols
Here is a list of types of endpoints which are supported by EMQ and accesible to N2O apps: WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, but for IoT and MQTT applications it could be served through UDP or SCTP protocols providing application level message delivery consistency.
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 Unfriendly developer community
Developers are often rude and unfriendly to users.
Con Bad documentation
It has bad documentation, which leaves out crucial steps, making it hard to learn.
