Alternatives to Apache Tomcat logo

Alternatives to Apache Tomcat

JBoss, Microsoft IIS, NGINX, Jetty, and Flask are the most popular alternatives and competitors to Apache Tomcat.
16.4K
12.3K
+ 1
201

What is Apache Tomcat and what are its top alternatives?

Apache Tomcat is an open-source implementation of the Java Servlet, JavaServer Pages, Java Expression Language, and Java WebSocket technologies. It is widely used for developing and deploying Java-based web applications. Key features of Apache Tomcat include cross-platform support, scalability, high performance, and integration with other Apache projects. However, some limitations of Tomcat include complex configuration settings and slower response times compared to some other servers.

  1. Jetty: Jetty is a lightweight and highly scalable Java-based web server and servlet container. It is known for its simplicity, speed, and low memory footprint. The key features of Jetty include support for different protocols, pluggable architecture, and integration with various Java frameworks. Pros of Jetty include fast startup time and low resource consumption, while its cons may include less robust administrative features compared to Tomcat.
  2. Undertow: Undertow is a lightweight and high-performance web server written in Java. It offers a flexible and efficient API for building web applications. Key features of Undertow include non-blocking I/O, HTTP/2 support, and easy integration with various Java frameworks. Pros of Undertow include high performance and low resource usage, while potential cons may include a steeper learning curve for beginners.
  3. WildFly: WildFly, formerly known as JBoss Application Server, is a popular open-source Java application server that includes a servlet container. It offers a wide range of features such as clustering, management capabilities, and support for the latest Java EE specifications. Pros of WildFly include robust security features and extensive documentation, while its cons may include a more complex setup compared to Tomcat.
  4. GlassFish: GlassFish is an open-source Java EE application server that provides a Java web server environment. It supports the latest Java EE specifications and offers features like clustering, monitoring, and administration tools. Pros of GlassFish include its compliance with Java EE standards and extensive tooling, while its cons may include a larger memory footprint compared to Tomcat.
  5. Payara Server: Payara Server is an open-source application server derived from GlassFish. It offers a lightweight, flexible, and stable platform for deploying Java EE applications. Key features of Payara Server include scalability, reliability, and support for microservices architecture. Pros of Payara Server include regular updates and patches, while its cons may include potentially limited community support compared to Tomcat.
  6. Resin: Resin is a fast and reliable Java application server that includes a servlet container. It is known for its performance, scalability, and ease of use. Key features of Resin include clustering, load balancing, and support for the latest Java EE standards. Pros of Resin include high performance and stability, while its cons may include fewer third-party integrations compared to Tomcat.
  7. Winstone: Winstone is a small, lightweight, and standalone servlet container that can be embedded in Java applications. It is designed for simplicity and ease of use, making it suitable for small projects. Pros of Winstone include its simplicity and small footprint, while its cons may include limited features compared to full-fledged application servers like Tomcat.
  8. WebLogic Server: WebLogic Server is a robust and feature-rich Java EE application server from Oracle. It offers advanced capabilities for enterprise-level applications, including high availability, scalability, and management tools. Pros of WebLogic Server include its comprehensive features and support for large-scale deployments, while its cons may include higher licensing costs and complexity compared to Tomcat.
  9. Jboss EAP: JBoss Enterprise Application Platform (EAP) is a commercially supported version of WildFly that provides enterprise-level features for developing and deploying Java applications. It offers enhanced security, performance, and support options. Pros of JBoss EAP include its stability and professional support, while its cons may include higher costs compared to using open-source servers like Tomcat.
  10. IBM WebSphere Application Server: IBM WebSphere Application Server is a Java EE-compliant application server that offers a range of features for building and running enterprise applications. It provides tools for development, testing, deployment, and monitoring of Java applications. Pros of WebSphere Application Server include its comprehensive features and integration with other IBM products, while its cons may include higher resource requirements and licensing costs compared to Tomcat.

Top Alternatives to Apache Tomcat

  • JBoss
    JBoss

    An application platform for hosting your apps that provides an innovative modular, cloud-ready architecture, powerful management and automation, and world class developer productivity. ...

  • Microsoft IIS
    Microsoft IIS

    Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks. ...

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Jetty
    Jetty

    Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty. ...

  • Flask
    Flask

    Flask is intended for getting started very quickly and was developed with best intentions in mind. ...

  • GlassFish
    GlassFish

    An Application Server means, It can manage Java EE applications You should use GlassFish for Java EE enterprise applications. The need for a seperate Web server is mostly needed in a production environment. ...

  • Websphere
    Websphere

    It is a highly scalable, secure and reliable Java EE runtime environment designed to host applications and microservices for any size organization. It supports the Java EE, Jakarta EE and MicroProfile standards-based programming models. ...

  • Wildfly
    Wildfly

    It is a flexible, lightweight, managed application runtime that helps you build amazing applications. It supports the latest standards for web development. ...

Apache Tomcat alternatives & related posts

JBoss logo

JBoss

335
253
0
An open source Java EE-based application server
335
253
+ 1
0
PROS OF JBOSS
    Be the first to leave a pro
    CONS OF JBOSS
      Be the first to leave a con

      related JBoss posts

      Microsoft IIS logo

      Microsoft IIS

      15.3K
      7.6K
      236
      A web server for Microsoft Windows
      15.3K
      7.6K
      + 1
      236
      PROS OF MICROSOFT IIS
      • 83
        Great with .net
      • 55
        I'm forced to use iis
      • 27
        Use nginx
      • 18
        Azure integration
      • 15
        Best for ms technologyes ms bullshit
      • 10
        Fast
      • 6
        Reliable
      • 6
        Performance
      • 4
        Powerful
      • 3
        Simple to configure
      • 3
        Webserver
      • 2
        Easy setup
      • 1
        Shipped with Windows Server
      • 1
        Ssl integration
      • 1
        Security
      • 1
        Охуенный
      CONS OF MICROSOFT IIS
      • 1
        Hard to set up

      related Microsoft IIS posts

      Farzeem Diamond Jiwani
      Software Engineer at IVP · | 8 upvotes · 1.4M views

      Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.

      Current Environment: .NET Core Web app hosted on Microsoft IIS

      Future Environment: Web app will be hosted on Microsoft Azure

      Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server

      Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.

      Please advise on the above. Thanks!

      See more
      Chris Bleck
      Site Reliability Engineer at Cooperative Bank Of Thessaly · | 5 upvotes · 15.7K views

      We are a small bank and we have 5 VMware ESXi servers with mainly Windows Server VMs with numerous windows services installed and most of these servers have Microsoft SQL Server and Microsoft IIS installed. Also we have some applications that have application logs (mainly in a db table) and we have a few Hangfire instances and one MQ Series server.

      Now the management gave me the task of site reliability (I'm fairly new to this) which means all Windows Services must run 24/7 so I have to know if a service fails to start. All databases must run properly so I have to know locks, Query performance, and any SQL Agent job failures. The same goes for IIS websites/services must be up and running all the time.

      In addition to these, I must collect all the Hangfire job failures(which are a lot) as well as general server metrics like CPU, RAM, I/O Disk, Disk sizes, etc.

      On top of all these, I must setup alerts via Slack/sms or mail. Now the question which tool or a stack of tools can achieve all that?

      See more
      NGINX logo

      NGINX

      112.6K
      60.4K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      112.6K
      60.4K
      + 1
      5.5K
      PROS OF NGINX
      • 1.4K
        High-performance http server
      • 893
        Performance
      • 730
        Easy to configure
      • 607
        Open source
      • 530
        Load balancer
      • 289
        Free
      • 288
        Scalability
      • 226
        Web server
      • 175
        Simplicity
      • 136
        Easy setup
      • 30
        Content caching
      • 21
        Web Accelerator
      • 15
        Capability
      • 14
        Fast
      • 12
        High-latency
      • 12
        Predictability
      • 8
        Reverse Proxy
      • 7
        The best of them
      • 7
        Supports http/2
      • 5
        Great Community
      • 5
        Lots of Modules
      • 5
        Enterprise version
      • 4
        High perfomance proxy server
      • 3
        Embedded Lua scripting
      • 3
        Streaming media delivery
      • 3
        Streaming media
      • 3
        Reversy Proxy
      • 2
        Blash
      • 2
        GRPC-Web
      • 2
        Lightweight
      • 2
        Fast and easy to set up
      • 2
        Slim
      • 2
        saltstack
      • 1
        Virtual hosting
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 1
        Ingress controller
      CONS OF NGINX
      • 10
        Advanced features require subscription

      related NGINX posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 10M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      John-Daniel Trask
      Co-founder & CEO at Raygun · | 19 upvotes · 267.6K views

      We chose AWS because, at the time, it was really the only cloud provider to choose from.

      We tend to use their basic building blocks (EC2, ELB, Amazon S3, Amazon RDS) rather than vendor specific components like databases and queuing. We deliberately decided to do this to ensure we could provide multi-cloud support or potentially move to another cloud provider if the offering was better for our customers.

      We’ve utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an nginx instance and are managed using scaling groups in Amazon EC2 sitting behind a standard AWS Elastic Load Balancing (ELB).

      While we’re satisfied with AWS, we do review our decision each year and have looked at Azure and Google Cloud offerings.

      #CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy

      See more
      Jetty logo

      Jetty

      468
      308
      43
      An open-source project providing an HTTP server, HTTP client, and javax.servlet container
      468
      308
      + 1
      43
      PROS OF JETTY
      • 14
        Lightweight
      • 10
        Very fast
      • 9
        Embeddable
      • 5
        Scalable
      • 5
        Very thin
      CONS OF JETTY
      • 0
        Student

      related Jetty posts

      Flask logo

      Flask

      18.9K
      15.9K
      82
      A microframework for Python based on Werkzeug, Jinja 2 and good intentions
      18.9K
      15.9K
      + 1
      82
      PROS OF FLASK
      • 14
        Flexibilty
      • 10
        For it flexibility
      • 9
        Flexibilty and easy to use
      • 8
        Flask
      • 7
        User friendly
      • 6
        Secured
      • 5
        Unopinionated
      • 3
        Orm
      • 2
        Secure
      • 1
        Beautiful code
      • 1
        Easy to get started
      • 1
        Easy to develop and maintain applications
      • 1
        Not JS
      • 1
        Easy to use
      • 1
        Documentation
      • 1
        Python
      • 1
        Minimal
      • 1
        Lightweight
      • 1
        Easy to setup and get it going
      • 1
        Perfect for small to large projects with superb docs.
      • 1
        Easy to integrate
      • 1
        Speed
      • 1
        Get started quickly
      • 1
        Customizable
      • 1
        Simple to use
      • 1
        Powerful
      • 1
        Rapid development
      • 0
        Open source
      • 0
        Well designed
      • 0
        Productive
      • 0
        Awesome
      • 0
        Expressive
      • 0
        Love it
      CONS OF FLASK
      • 10
        Not JS
      • 7
        Context
      • 5
        Not fast
      • 1
        Don't has many module as in spring

      related Flask posts

      James Man
      Software Engineer at Pinterest · | 46 upvotes · 2.8M views
      Shared insights
      on
      FlaskFlaskReactReact
      at

      One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

      Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

      Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

      See more

      Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

      See more
      GlassFish logo

      GlassFish

      312
      111
      0
      The Open Source Java EE Reference Implementation
      312
      111
      + 1
      0
      PROS OF GLASSFISH
        Be the first to leave a pro
        CONS OF GLASSFISH
          Be the first to leave a con

          related GlassFish posts

          Websphere logo

          Websphere

          98
          92
          0
          Application and integration middleware
          98
          92
          + 1
          0
          PROS OF WEBSPHERE
            Be the first to leave a pro
            CONS OF WEBSPHERE
              Be the first to leave a con

              related Websphere posts

              Wildfly logo

              Wildfly

              184
              225
              6
              A Java EE8 Application Server
              184
              225
              + 1
              6
              PROS OF WILDFLY
              • 3
                Eclipse integration
              • 3
                Java
              CONS OF WILDFLY
                Be the first to leave a con

                related Wildfly posts

                Shared insights
                on
                KeycloakKeycloakWildflyWildfly

                I have an EAR deployed in a Wildfly instance. And it has many WAR folders. Is it possible to secure the whole EAR with Keycloak? And if I want to secure some of the WAR inside that EAR with Keycloak, is that possible?

                See more