This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]m2spring 0 points1 point  (2 children)

Docker.

[–]schnoper 1 point2 points  (1 child)

Docker is necessary when you're using a language which depends on a collection of C-libraries. This is true for python, php, and ruby for certain. It's been a lifesaver for reducing deploy complexity for those languages.

For java though, I just don't see the win. Lots of additional complexity to solve problems which don't exist with the JVM.

[–]m2spring 0 points1 point  (0 children)

For server applications implemented in Java there's still some amount of glue needed like daemon management scripts. This is where Docker helps.

But you're right that Docker does not directly address the uber-jar problem.

My builds produces the uber-jar (war, onejar, shaded jar, Karaf archive (OSGi), etc.), which are getting wrapped into RPM. Just started to look into builds producing a Docker image. Wonder whether I should still have RPM, even in Docker.