October 11, 2016
Score 7 out of 10
Overall Satisfaction with Apache Tomcat
Tomcat was our main server. We used it both in our local machines and we ran it in our Amazon Web Services host. This was only being used by the engineering team because no other teams needed to know what server we were running. In addition, it was only our web team that dealt with the actual server.
- The server is easy to install, start up and shut down.
- It integrates very cleanly with Eclipse.
- It's supported by AWS which makes deployments very smooth.
- Because it's Java-based, you typically must re-compile to make use of updates which can drastically increase development time.
- It was slightly painful to get set up in Eclipse relative to other newer solutions.
- It would be nice if it were easier and more intuitive to make changes to the server configurations.
- The positive impact is its universal support. It's easy to spin up a server and then deploy it to AWS.
- The negative impact is the speed at which development occurs. Relative to a back end built on a scripting language, development time is much slower.
- Overall, it's allowed us to scale the web site as the company grows.
Relative to other solutions that worked with the Spring framework, Tomcat was the best. It worked exactly as desired and made releasing production builds a very smooth process. However, if I were able to choose, I would use one of the newer scripting languages that has a server built in - for example, Node/Express, Python/Django, or Ruby on Rails.
If you want to use Java or the Spring framework, you need to be using Tomcat. However, this is probably best for larger companies. If you're a startup looking to move quickly, it may not be the best choice. However, it is well tested and universally supported, so I would highly suggest using it if you are set on being a Java shop.