Menu
We're looking at converting some of our legacy JaveEE apps over to Spring Boot. We're getting a vendor in to perform this, but they claim that Spring boot with embedded Tomcat or Jetty is not production ready and instead recommend us to still package it for deployment into a container (either Tomcat/Jetty or JBoss). This kinds of defeats the purpose. Is the claim accurate?
515
The Spring Boot starters ( spring-boot-starter-web in particular) use Tomcat as an embedded container by default. You need to exclude those dependencies and include the Jetty one instead.
By default, Spring boot uses embedded tomcat server to run the application. At times, you may need to use jetty server in place of tomcat server. Spring Boot provides Tomcat and Jetty dependencies bundled together as separate starters to help make this process as easy as possible.
Spring Boot is a popular Java-based framework to develop microservices. By default, the Spring Tool Suite (STS) IDE -- which is used to build a Spring Boot application -- will automatically create an embedded Tomcat server with the microservices developed each time a build or deployment occurs.
Tomcat 7 & 8.0 work with Spring Boot, but the default is to use Tomcat 8.5. If you cannot use Tomcat 8.5 (for example, because you are using Java 1.6) you will need to change your classpath to reference a different version.
The Spring team recommends the standalone "embedded mode", Pivotal (Spring's corporate sponsor) provides major consulting services and recommends embedded mode, and Netflix has reengineered large sections of its systems to run on standalone Boot.
I've been using embedded mode (Tomcat and now Undertow) since 0.5.0M6 and have never had a problem with the server component. Sounds like maybe your vendor has a problem to sell you.
100
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
