Spring and Dropwizard are really not comparable. Spring is a large, invasive framework which covers many different facets of enterprise application design. Dropwizard is a set of commonly-used libraries (jetty, jersey, jackson, slf4j, a couple others) with a little bit of glue to stitch them together.
Very well stated. You said it in half the words I did. I especially like your point about Spring being "invasive". For me, Spring MVC was so invasive I couldn't justify using it... the LDAP, JDBC, and Security components work usable without too much interference though.
Comments
Spring and Dropwizard are really not comparable. Spring is a large, invasive framework which covers many different facets of enterprise application design. Dropwizard is a set of commonly-used libraries (jetty, jersey, jackson, slf4j, a couple others) with a little bit of glue to stitch them together.
Very well stated. You said it in half the words I did. I especially like your point about Spring being "invasive". For me, Spring MVC was so invasive I couldn't justify using it... the LDAP, JDBC, and Security components work usable without too much interference though.