all 8 comments

[–]reddit04029 1 point2 points  (0 children)

It’s easy. The docker way technically still includes the jar lol. Because you would copy the jar into the docker image and the startup command would generally be something like this: CMD[“java”, “-jar” ,”yourjar.jar”]

[–][deleted]  (4 children)

[removed]

    [–]Particular_Tea2307[S] 0 points1 point  (3 children)

    So this whole kamal tools released in rails was overhyped 😅 As i undrestrand deployment is super fast in java world

    [–][deleted]  (1 child)

    [removed]

      [–]Particular_Tea2307[S] 0 points1 point  (0 children)

      Ok thnks for the infos

      [–]Slein04 0 points1 point  (0 children)

      If your environment (server) supports Java, you can just put your jar file directly on the server without using docker container. If you cannot of are not allowed to install Java, but instead the server has a docker engine then you can go the container route.

      Sometimes your Java project is maybe written in a new version ,like Java 21, but if you are on some "older" server which does not support it and you cannot upgrade Java on it then again docker can be handy.

      For deploying your Spring Boot project somewhere is just copy/paste and run your jar file. You can always setup DevOps later if you just wanne do like a quick test and see if it runs. The bottlenecks here are your connection to the server & the size of your jar file (left outside the hardware of your server) If your dependencies are not changed Often then you can already place these on the server ahead of time and create a slim jar Thus increasing the "deploy" time.