-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Docker images size smaller #889
Comments
Spring boot packages a tomcat inside the jar that it creates. Isn't it actually more bulky? I am not saying that it's a bad idea, but what is the goal here? |
Oh, does it? So I didn't put that question mark for nothing :)) For some reason I thought Spring boot had its own http engine. |
Just to clarify. I'm not against WAR-files, in fact I see a lot of strengths in this tech. I'm just wandering if there is anything more modern and significantly more lightweight in the micro-services and Docker era. But by default I'd stick with the current stack. |
As far as I know Spring boot doesn't add many new features to spring. It mostly provides opinioned default configuration for all other spring parts that makes everything work out of the box. In Boot, you can choose Tomcat, Jetty or Undertow as a servlet container. An interesting alternative to Spring-MVC might also be Spring Web Reactive. Which claims to be functional and fully asynchronous. Spring Web Reactive by default runs on all mentioned servers plus on Netty server. |
As it turns out Tomcat slim image is already quite compact where the largest part is the OS layer. So no further image size optimization is needed at this stage IMO |
I'll replace JDK with JRE and use |
Since more and more people are using Docker containers over standalone J2EE servers, I see no reason to continue supporting the later. We should switch to a lighter container (Spring boot?).
The text was updated successfully, but these errors were encountered: