Apache Tomcat vs. Jenkins

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Tomcat
Score 8.8 out of 10
N/A
Tomcat is an open-source web server supported by Apache.N/A
Jenkins
Score 8.3 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.N/A
Pricing
Apache TomcatJenkins
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache TomcatJenkins
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache TomcatJenkins
Considered Both Products
Apache Tomcat
Chose Apache Tomcat
Tomcat stacks up against the others very well due to its adoption in the open source community, low total cost of ownership, maintenance, and ease of deployment. It's much more lightweight than Websphere or Weblogic and provides most of the features most developers would need, …
Jenkins

No answer on this topic

Top Pros
Top Cons
Features
Apache TomcatJenkins
Application Servers
Comparison of Application Servers features of Product A and Product B
Apache Tomcat
8.9
24 Ratings
10% above category average
Jenkins
-
Ratings
IDE support8.922 Ratings00 Ratings
Security management8.524 Ratings00 Ratings
Administration and management8.324 Ratings00 Ratings
Application server performance8.224 Ratings00 Ratings
Installation9.924 Ratings00 Ratings
Open-source standards compliance9.324 Ratings00 Ratings
Best Alternatives
Apache TomcatJenkins
Small Businesses
NGINX
NGINX
Score 9.1 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache TomcatJenkins
Likelihood to Recommend
8.9
(24 ratings)
8.2
(69 ratings)
Likelihood to Renew
10.0
(1 ratings)
-
(0 ratings)
Usability
8.0
(3 ratings)
5.0
(3 ratings)
Availability
6.0
(1 ratings)
-
(0 ratings)
Performance
9.0
(2 ratings)
8.9
(6 ratings)
Support Rating
9.1
(3 ratings)
6.6
(6 ratings)
Configurability
8.0
(1 ratings)
-
(0 ratings)
Ease of integration
9.0
(1 ratings)
-
(0 ratings)
Product Scalability
9.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apache TomcatJenkins
Likelihood to Recommend
Apache
Excellent value for companies wishing to host Java applications in the cloud. Utilizing hosting tools such as load balancers and network and application firewalls, Tomcat can be part of a powerful system to host web applications to thousands of users. There has been consistency in the development and support of Tomcat since its initial release in the late '90s and the best commonalities have been carried forward. If you host Java web applications, Tomcat is as good as any for an application server.
Read full review
Open Source
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Read full review
Pros
Apache
  • Fast to start up, which is useful when we need to just check that our changes are working correctly.
  • Free, which allows us to not be involved with the finance/legal team about using it.
  • Bundled with Spring Boot, which makes it even more convenient for our testing.
Read full review
Open Source
  • Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
  • Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
  • Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
Read full review
Cons
Apache
  • Using tomcat manager to troubleshoot is not very informative. Error messages are vague, you have to dig into log files for more information about the problems.
  • Is great for simple web applications, but may not work for heavy development which may require a full J2EE stack, might like JBoss better.
  • Security in tomcat is not straightforward, as I discovered that you have to understand how to set up realms in tomcat in order to hash passwords, which I was not overly familiar with, which is a big deal when setting up users in the tomcat-users.xml file.
Read full review
Open Source
  • The UI could be slightly better, it feels kind of like the 90s, but it works well.
  • An easier way to filter jobs other than views on the dashboard.
  • An easier way to read the console logs when tests do fail.
Read full review
Likelihood to Renew
Apache
We have a huge knowledge of the product within our company and we're satisfied with the performance.
Read full review
Open Source
No answers on this topic
Usability
Apache
Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.
Read full review
Open Source
While the day to day use is very easy, the configuration and setting up of the system or new projects can be cumbersome.
Read full review
Reliability and Availability
Apache
Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.
Read full review
Open Source
No answers on this topic
Performance
Apache
Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.
Read full review
Open Source
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
Read full review
Support Rating
Apache
Well, in actuality, I have never needed support for Apache Tomcat since it is configured and ready-to-go with no configuration needed on my end.
Read full review
Open Source
There is a large development community - but it is shifting as people move towards other tools. A lot of companies still use Jenkins and will build propriety tools, which doesn't help any of the open-source community. Jenkins has a lot of help and support online, but other, more modern, alternatives will have better support for newer tech.
Read full review
Alternatives Considered
Apache
Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it requires less memory to operate, you may realize that it is very efficient.
Read full review
Open Source
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
Read full review
Scalability
Apache
It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm
Read full review
Open Source
No answers on this topic
Return on Investment
Apache
  • Tomcat is cheap and very quick to deploy, so it has benefited much when situation needs applications to be deployed quickly without wasting time on licensing and installations.
  • Plenty of documentation available so no vendor training is required. Support contract is not needed as well.
Read full review
Open Source
  • Faster Time-to-Market: Jenkins automate the build, testing, and deployment process, enabling faster feedback and continuous improvement.
  • Improved Quality: Jenkins automatically run unit tests and integration tests, ensuring that code changes meet the necessary quality standards.
  • Cost Savings: Jenkins is an open-source tool that is free to use
Read full review
ScreenShots