Speed up the launch of your light-weighted Web application/service
February 16, 2018
Speed up the launch of your light-weighted Web application/service
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Apache Tomcat
We use tomcat bundled with the SpringBoot in Fedex IT departments, majorly for small/middle-scaled and light-weighted web application and RESTful based micro services. Those light applications are supposed to be containerized to support the cloud-native initiative. Also for a quick POC purpose, we use Tomcat as the light solution to host some pure servlet based codes.
- tomcat is very light-weighted, that means a small memory footprint and a very quick starting time
- It also supports the modern security demands well
- Using the version bundled with the SpringBoot, saving the extra deployment efforts, making your single JVM application become the quick web service solution easily
- tomcat is just part of the J2EE specification implementation, majorly focusing on the servlet (front-end) part. If you requires the full J2ee stack, like EJB support, you need consider other containers like Weblogic
- tomcat's cluster level support is very limited
- tomcat's admin/configuration is not so intuitive, and default logging needs a lot of improvement
- tomcat makes the POC much more efficient, speeding up the early phase of decision making, and concept proof, shortened the project planning phase required time
- tomcat saves the extra training and resources for web container management, typically when it is used with bundled Spring Boot
We use WebLogic as an enterprise level large application container. We have a big WebLogic cluster, hosting our core applications. We also use tomcat to build a quick POC and some light-weighted RESTful service for a cloud-native initiative, so the relationship should be complete with each other.