TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Tomcat

    Score7.9 out of 10
    N/ATomcat is an open-source web server supported by Apache.N/A

    GitHub

    Score9.2 out of 10
    N/AGitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.

    $4

    per month per user

    Jenkins

    Score8.1 out of 10
    N/AJenkins 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 TomcatGitHubJenkins
    Editions & Modules
    No answers on this topic
    Team
    $40
    per year per user
    Enterprise
    $210
    per year per user
    No answers on this topic
    Offerings
    Pricing Offerings
    Apache TomcatGitHubJenkins
    Free Trial
    NoYesNo
    Free/Freemium Version
    NoYesYes
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details———
    More Pricing Information
    Community Pulse
    Apache TomcatGitHubJenkins
    Considered Multiple Products
    Apache
    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, …
    Incentivized
    GitHub
    Chose GitHub
    Microsoft Team Foundation Server was too heavy and too complex for fast dvelopment. The integration with opensource build solutions (i.e jenkins) was not explored but the main feedback on this tool was its complexity.
    CVS and SVN used to be standards in past years and fit …
    Incentivized
    Chose GitHub
    GitHub is the best platform to manage your source code. You can manage your CI/CD with different cloud service provider platforms and different languages. You can also create GHE for a number of organizations and repositories. Learning GitHub is easy and simple and supports …
    Incentivized
    Chose GitHub
    Gitlab is something that I would investigate more if I need an on-site solution. Bitbucket has a terrible UX like most Atlassian products.
    Incentivized
    Chose GitHub
    • So the far the best UI representation of code which helps the team co-ordinate easier.
    • Easy to explore other projects in an organization and also view a developers performance and history of code writtern in a year.
    • An issue that can be created as part of the GitHub Repo instead …
    Incentivized
    Chose GitHub
    Bitbucket supports Mercurial VCS in addition to Git. Since it is an Atlassian product, Bitbucket is very well integrated with the company's other tools, like JIRA (which is widely used in the development industry), Jenkins, and Bamboo. It offers many of the same features as …
    Incentivized
    Chose GitHub
    An integrated issue tracker right within your project.
    Milestones and labels within projects.
    Branch comparison views
    Incentivized
    Chose GitHub
    Github is far superior to Svn source control. The speed is a big plus for large projects.
    Incentivized
    Chose GitHub
    Bitbucket has an interface that is much uglier and much more confusing to use. The learning curve is therefore much greater with Bitbucket. However, Bitbucket allows for free private repositories for small teams, which is a huge plus, and if your team is small enough, that …
    Incentivized
    Open Source
    Chose Jenkins
    GitLab CI and GitHub Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform.
    But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime …
    Incentivized
    Chose Jenkins
    Jenkins is highly customizable and flexible, supporting a wide range of plugins and integrations. Jenkins works with any version control system (Git, Subversion, etc.). Jenkins has a more mature ecosystem, and it may be better for large-scale, complex environments, especially …
    Incentivized
    Chose Jenkins
    I have used Spinnaker as a CD tool. Though it's a very powerful CD tool we still needed Jenkins for CI, so to save some hassle for us we opt Jenkins solely.
    Incentivized
    Chose Jenkins
    It's mostly stable and well-known within the DevOps community.
    Incentivized
    Chose Jenkins
    Both Jenkins and TeamCity do a good job of automating CI/CD. Jenkins runs much leaner than TeamCity - it only needs about a Gig of free memory, whereas TeamCity needs a fat 4 Gig free. Many tasks in Jenkins yml config can be very cumbersome, especially running local and …
    Incentivized
    Chose Jenkins
    Jenkins is the only solution that we've tried that just automatically generates builds.
    Incentivized
    Chose Jenkins
    I don't have any experience with alternatives to Jenkins.
    Incentivized
    Chose Jenkins
    Jenkins has been my favorite continuous integration tool I've used. It's easy to setup, intuitive to use, and very powerful. The software allows for building complex workflows, then having them run without thinking about it. This leads to savings in time and resources, and to …
    Incentivized
    Chose Jenkins
    When looking for alternatives for Jenkins we found CircleCI and TeamCity are good too. Jenkins was considered for reasons like it has a wide variety of plugins which integrate well with any kind of system. And its ease of use.

    One of the other greater advantage is it is open …
    Incentivized
    Chose Jenkins
    I had experienced some outages and bugs with CircleCI which can be very frustrating since you don't have control over the software.
    Incentivized
    Chose Jenkins
    TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCi…
    Incentivized
    Chose Jenkins
    Jenkins immense flexibility and its large and impressive selection of available community-driven plugins makes it ideal choice for solving non-traditional problems.

    However, for CI/CD - consider the benefit of modern tools that enforce reusable, infrastructure as code design …
    Incentivized
    Chose Jenkins
    Travis CI and AppVeyor are good services that provide rudimentary support for builds, but they focus on Linux/OSX and Windows respectively, meaning that cross-platform builds will need to use both services. They are free for open source projects on GitHub, so they are seen …
    Incentivized
    Chose Jenkins
    Jenkins provides bare metal framework that people would be able to use and transform to their needs. In a lot of other cases, there are lot of configurations already available which make the softwares heavy ended and less customizable. Also, there are a lot of open source …
    Incentivized
    Chose Jenkins
    Jenkins is ideal for developing software with high-security demands. It is hosted and set up locally and has no outside connections. But these pros could become cons when you work on open source projects and need to waste time for initial setup and maintenance over a project's …
    Incentivized
    Chose Jenkins
    I have not evaluated any other solutions as I was just a user.
    Incentivized
    Key User Insights
    Would buy again
    100%
    Would buy again
    8 Answers
    96%
    Would buy again
    47 Answers
    87%
    Would buy again
    26 Answers
    Delivers good value for the price
    100%
    Delivers good value for the price
    8 Answers
    98%
    Delivers good value for the price
    46 Answers
    100%
    Delivers good value for the price
    27 Answers
    Happy with the feature set
    100%
    Happy with the feature set
    8 Answers
    98%
    Happy with the feature set
    48 Answers
    87%
    Happy with the feature set
    26 Answers
    Lived up to sales and marketing promises
    100%
    Lived up to sales and marketing promises
    6 Answers
    95%
    Lived up to sales and marketing promises
    38 Answers
    93%
    Lived up to sales and marketing promises
    13 Answers
    Implementation went as expected
    100%
    Implementation went as expected
    8 Answers
    100%
    Implementation went as expected
    42 Answers
    96%
    Implementation went as expected
    22 Answers
    Features
    Apache TomcatGitHubJenkins
    Application Servers
    Comparison of Application Servers features of Apache Tomcat and GitHub and Jenkins
    Feature
    Apache Tomcat
    9.2
    24 Ratings
    15% above category average
    GitHub
    -
    Ratings
    Jenkins
    -
    Ratings
    IDE support10.022 Ratings00 Ratings00 Ratings
    Security management9.024 Ratings00 Ratings00 Ratings
    Administration and management8.224 Ratings00 Ratings00 Ratings
    Application server performance8.124 Ratings00 Ratings00 Ratings
    Installation10.024 Ratings00 Ratings00 Ratings
    Open-source standards compliance10.024 Ratings00 Ratings00 Ratings
    Version Control Software Features
    Comparison of Version Control Software Features features of Apache Tomcat and GitHub and Jenkins
    Feature
    Apache Tomcat
    -
    Ratings
    GitHub
    9.4
    10 Ratings
    7% above category average
    Jenkins
    -
    Ratings
    Branching and Merging00 Ratings9.710 Ratings00 Ratings
    Version History00 Ratings9.710 Ratings00 Ratings
    Version Control Collaboration Tools00 Ratings9.89 Ratings00 Ratings
    Pull Requests00 Ratings9.710 Ratings00 Ratings
    Code Review Tools00 Ratings8.89 Ratings00 Ratings
    Project Access Control00 Ratings9.210 Ratings00 Ratings
    Automated Testing Integration00 Ratings8.810 Ratings00 Ratings
    Issue Tracking Integration00 Ratings8.910 Ratings00 Ratings
    Branch Protection00 Ratings9.89 Ratings00 Ratings
    Best Alternatives
    Apache TomcatGitHubJenkins
    Small Businesses
    NGINX
    Score9.1 out of 10
    Git
    Score10 out of 10
    Apache Maven
    Score9.1 out of 10
    Medium-sized Companies
    Oracle WebLogic Server
    Score7.3 out of 10
    Git
    Score10 out of 10
    Apache Maven
    Score9.1 out of 10
    Enterprises
    NGINX
    Score9.1 out of 10
    Perforce P4
    Score7.6 out of 10
    Gradle Build Tool (Open Source)
    Score9 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Apache TomcatGitHubJenkins
    Likelihood to Recommend
    9.0
    (24 ratings)
    9.9
    (131 ratings)
    6.8
    (74 ratings)
    Likelihood to Renew
    10.0
    (1 ratings)
    10.0
    (1 ratings)
    -
    (0 ratings)
    Usability
    8.0
    (3 ratings)
    9.4
    (10 ratings)
    6.4
    (8 ratings)
    Availability
    6.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    Performance
    9.0
    (2 ratings)
    -
    (0 ratings)
    8.9
    (6 ratings)
    Support Rating
    9.1
    (3 ratings)
    8.8
    (26 ratings)
    6.6
    (6 ratings)
    Implementation Rating
    -
    (0 ratings)
    -
    (0 ratings)
    6.0
    (1 ratings)
    Configurability
    8.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    Ease of integration
    9.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    Product Scalability
    9.0
    (1 ratings)
    -
    (0 ratings)
    -
    (0 ratings)
    User Testimonials
    Apache TomcatGitHubJenkins
    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.
    Incentivized
    Read full review
    GitHub
    GitHub is an easy to go tool when it comes to Version Controlling, CI/CD workflows, Integration with third party softwares. It's effective for any level of CI/CD implementation you would like to. Also the the cost of product is also very competitive and affordable. As of now GitHub lacks capabilities when it comes to detailed project management in comparison to tools like Jira, but overall its value for money.
    Incentivized
    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.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    • Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
    • Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
    • Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
    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.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    • Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
    • Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
    • Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
    • While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
    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.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
    Read full review
    Open Source
    We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
    Incentivized
    Read full review
    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.
    Incentivized
    Read full review
    GitHub
    GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
    Incentivized
    Read full review
    Open Source
    Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    No answers on this topic
    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.
    Incentivized
    Read full review
    GitHub
    No answers on this topic
    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.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    There are a ton of resources and tutorials for GitHub online. The sheer number of people who use GitHub ensures that someone has the exact answer you are looking for. The docs on GitHub itself are very thorough as well. You will often find an official doc along with the hundreds of independent tutorials that answers your question, which is unusual for most online services.
    Incentivized
    Read full review
    Open Source
    As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
    Incentivized
    Read full review
    Implementation Rating
    Apache
    No answers on this topic
    GitHub
    No answers on this topic
    Open Source
    It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
    Incentivized
    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.
    Incentivized
    Read full review
    GitHub
    While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their integration will likely be much tighter. Gitlab on the other hand has a reputation as a very capable GitHub replacement with some features that are not available on GitHub like firewall tools.
    Incentivized
    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.
    Incentivized
    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
    Incentivized
    Read full review
    GitHub
    No answers on this topic
    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.
    Incentivized
    Read full review
    GitHub
    • Team collaboration significantly improved as everything is clearly logged and maintained.
    • Maintaining a good overview of items will be delivered wrt the roadmap for example.
    • Knowledge management and tracking. Over time a lot of tickets, issues and comments are logged. GitHub is a great asset to go back and review why x was y.
    Incentivized
    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
    Incentivized
    Read full review
    ScreenShots