StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. Apache Tomcat vs Undertow

Apache Tomcat vs Undertow

OverviewDecisionsComparisonAlternatives

Overview

Apache Tomcat
Apache Tomcat
Stacks16.9K
Followers12.6K
Votes201
GitHub Stars8.0K
Forks5.3K
Undertow
Undertow
Stacks49
Followers94
Votes5

Apache Tomcat vs Undertow: What are the differences?

Apache Tomcat and Undertow are both popular web servers and servlet containers used for hosting Java web applications. Let's explore the key differences between them.

  1. Architecture: Apache Tomcat is a monolithic application server that includes a built-in web server, whereas Undertow is a lightweight web server commonly used as a servlet container. Tomcat provides a complete Java EE application server environment, while Undertow focuses on delivering high-performance HTTP and WebSocket services.

  2. Embedded Capabilities: Undertow has stronger support for embedding within other Java applications. It provides a flexible API for programmatic configuration and direct integration, making it an ideal choice for microservices architectures and embedding within non-traditional server deployments. Tomcat, on the other hand, is primarily designed for standalone use and may require more effort to embed within other applications.

  3. Performance: Undertow is known for its high performance and low resource usage. It is built with an asynchronous, non-blocking architecture that enables it to handle a large number of concurrent connections efficiently, making it suitable for high-performance applications. Tomcat, while also capable of handling a significant number of connections, may have a slightly lower performance when compared to Undertow.

  4. Ease of Configuration: Tomcat provides a rich set of configuration options through XML-based configuration files, allowing fine-grained control over various server aspects. Undertow, on the other hand, offers a simpler and more lightweight configuration approach through Java code or properties files. This can be advantageous for developers who prefer programmatic configuration or desire a streamlined configuration process.

  5. Ecosystem Support: Apache Tomcat has been around for a longer time and has a larger community, making it more mature and widely adopted. It has an extensive ecosystem with numerous plugins, libraries, and documentation available. Undertow, although gaining popularity, may have a smaller ecosystem and fewer resources for support and guidance.

  6. Servlet Specification Compliance: Both Apache Tomcat and Undertow are compliant with the Java Servlet specification. However, Tomcat has a more extensive history and is typically quicker to implement new versions of the specification. This means that Tomcat may provide better compatibility with applications that rely on the latest servlet features or may have more specific servlet-related requirements.

In summary, Apache Tomcat is a feature-rich, widely adopted application server that provides a complete Java EE environment, while Undertow is a lightweight and high-performance web server suitable for embedding and microservices architectures. Undertow offers better performance, ease of configuration through code, and is well-suited for high-concurrency scenarios. However, Tomcat has a larger ecosystem, better community support, and may be more suitable for applications with complex Java EE requirements or specific servlet-related needs.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Apache Tomcat, Undertow

Hari
Hari

Mar 3, 2020

Needs advice

I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to

  1. configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly.
  2. Install apache and tomcat.
  3. Generate and apply selfsigned certs to http server.
  4. Modify default ports on Tomcat to different ports.
  5. Create users on RHEL for application support team.
  6. other administrative tasks like, start, stop and restart HTTP and Tomcat services.

I have utilized the power of ansible for all these tasks, which made it easy and manageable.

419k views419k
Comments

Detailed Comparison

Apache Tomcat
Apache Tomcat
Undertow
Undertow

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

It is a flexible performant web server written in java, providing both blocking and non-blocking API’s based on NIO. It has a composition based architecture that allows you to build a web server by combining small single purpose handlers. The gives you the flexibility to choose between a full Java EE servlet 4.0 container, or a low level non-blocking handler, to anything in between.

-
Flexible Web Server; composition based architecture
Statistics
GitHub Stars
8.0K
GitHub Stars
-
GitHub Forks
5.3K
GitHub Forks
-
Stacks
16.9K
Stacks
49
Followers
12.6K
Followers
94
Votes
201
Votes
5
Pros & Cons
Pros
  • 79
    Easy
  • 72
    Java
  • 49
    Popular
  • 1
    Spring web
Cons
  • 3
    Blocking - each http request block a thread
  • 2
    Easy to set up
Pros
  • 4
    Performance
  • 1
    Lower footprint
Cons
  • 1
    Smaller community
  • 1
    Less known
Integrations
No integrations available
Spring Boot
Spring Boot
Wildfly
Wildfly

What are some alternatives to Apache Tomcat, Undertow?

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.

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

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.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.

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.

lighttpd

lighttpd

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Swoole

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Puma

Puma

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase