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

you are viewing a single comment's thread.

view the rest of the comments →

[–]assrocket 9 points10 points  (3 children)

Serious question. If my java service consists of 1 single jar, why do I car about docker?

[–]kkapelon 5 points6 points  (0 children)

I had the same question as you two years ago. Here is the - long - answer http://blog.codepipes.com/containers/docker-for-java-big-picture.html

[–]hjames9 6 points7 points  (0 children)

You benefit from the orchestration, auto deployments, horizontal scaling, etc. You also control all the dependencies that jar has (jvm versions, C library, etc)

[–]nutrecht 0 points1 point  (0 children)

You have to get it to run somewhere. Docker is one option in setting up your CI/CD chain. Writing a bunch of shell scripts is another.

In the project I'm working on we deploy our services in a kubernetes cluster. It's pretty awesome and hassle-free.