Dropwizard is a bit heavy by Node standards. The health checks, in the NPM-style system, would be its own package. The configuration class would be its own package. Resources would be their own package. Liquibase or Freemarker wouldn't be built in, nor would JDBI.
I think of Dropwizard much like express for node, and most of the "cool kids" in the node community think that that's just too much for a single library.
I like Dropwizard, don't get me wrong, but it isn't quite a micro-framework by other standards.
I'm sorry, I may have been misunderstood. I meant that Dropwizard exemplifies how you can pick and choose components, those atomic libraries, into a "framework" of your choosing. Dropwizard contains very little code. It's just an assembly of the parts you wished existed, and the proof that those parts already exist.
That makes sense, then. Looking at the source code briefly, it looks very similar to what I mean, especially if the parts are able to be used individually.
I think of Dropwizard much like express for node, and most of the "cool kids" in the node community think that that's just too much for a single library.
I like Dropwizard, don't get me wrong, but it isn't quite a micro-framework by other standards.