Re:Debunking the Java Performance Myth
by traspler on Sunday October 22, 2017 @11:46AM
(#15527290)
One big drawback of Dropwizard (at least for us) was that it was very problematic to deploy it as a war in a tomcat environment. There is wizard-in-a-box but there were a lot of issues with that as well.
[ Parent
| on HN ]
Re:Debunking the Java Performance Myth
by RhodesianHunter on Sunday October 22, 2017 @01:13PM
(#15527793)
Yeah, that's definitely a square peg + round hole problem. Dropwizard is intended to be deployed as a "Fat Jar" and does not need tomcat/tomee.
This is nice because it makes it easier to treat your servers like disposable cattle when (almost) all of your configuration and dependencies live in your easily deployed Jar.
If you're deploying a dropwizard app as a war in tomcat you're doing something a bit odd.
True but sadly project specs sometimes change in odd ways.
Well, if you're doing microservices you're usually nullifying most of the benefits of this kind of architecture if you're just deploying them on war files on a single application container.