Jamie Perkins

Hey

Dropwizard

28 May 2015

As you may know, we have many REST APIs running on the JVM. The majority of which use the Spring MVC framework. We've very much a love/hate relationships with Spring (mostly hate).

An entire series of posts could be written about things we don't like about Spring, but to save time and sanity, I'll summarise as: too much boilerplate and configuration around merely getting the framework to serve HTTP requests. XML config files and ManagerServiceFactoryBeanImplFactory take time to understand and set up, leaving you less time to solve the problem that your application owes its existence to. We use annotations in most places to configure our Spring apps, but it's still a pain to have to deal with in general.

We've now moved two of our projects onto Dropwizard and are so far extremely happy with what we've seen.

What is Dropwizard?

It's a combination of things really as the Getting Started page will tell you. It provides Jetty for HTTP, Jackson for JSON, Jersey for REST and so on. The power and convenience of Dropwizard comes from it's hiding and pre-configuration of the above things right out of the box. To go from nothing to something serving API requests in Dropwizard doesn't require you to write a line of code setting up a Jetty or configuring Jackson.

Everything you need is exposed cleanly, everything you don't is hidden away. This leaves you to start writing code to solve problems almost immediately. The two projects I mentioned above were already using Jetty and Jersey, and so their migrations were fairly trivial. We will be moving Atlas Deer from Spring to Dropwizard sometime in the near future. I'll report back on how that goes and with any useful tips for moving from one to the other.

Example!

package com.metabroadcast.dropwizard.example;



import io.dropwizard.Application;
import io.dropwizard.setup.Bootstrap;
import io.dropwizard.setup.Environment;



public class ExampleApplication extends Application<ExampleConfiguration> {


public static void main(String[] args) throws Exception {
    new ExampleApplication().run(args);
}

@Override
public void run(ExampleConfiguration conf, Environment env) throws Exception {
    env.jersey().register(HelloWorldResource.class);
}



}

The above code, plus a very simple Configuration class and YAML, is all you need to start serving requests from an endpoint in Dropwizard. On top of that there is a long list of built-in, out of the box features that most if not all applications of this type would like.

An admin servlet is automatically configured and started, from which tasks and health checks can be easily built on top of. Other features include but are not limited to:

All come for free and only require you to implement the bit you care about.

I'll save going into much more depth for after we've moved a Spring application onto Dropwizard, as I expect there will be far more to show. But so far, we would seriously recommend checking it out!

Originally posted on MetaBroadcast's blog.

Related Posts