Alternatives to Undertow logo

Alternatives to Undertow

Wildfly, Apache Tomcat, Jetty, Grizzly, and Netty are the most popular alternatives and competitors to Undertow.
40
55
+ 1
5

What is Undertow and what are its top alternatives?

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.
Undertow is a tool in the Web Servers category of a tech stack.

Top Alternatives to Undertow

  • 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

    Apache Tomcat

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

  • 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. ...

  • Grizzly

    Grizzly

    Writing scalable server applications in the Java™ programming language has always been difficult. Before its advent, thread management issues made it impossible for a server to scale to thousands of users. This framework has been designed to help developers to take advantage of the Java™ NIO API. ...

  • Netty

    Netty

    Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server. ...

  • Spring Boot

    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • 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. ...

Undertow alternatives & related posts

Wildfly logo

Wildfly

158
163
5
A Java EE8 Application Server
158
163
+ 1
5
PROS OF WILDFLY
  • 3
    Java
  • 2
    Eclipse integration
CONS OF WILDFLY
    Be the first to leave a con

    related Wildfly posts

    Apache Tomcat logo

    Apache Tomcat

    12.5K
    8.9K
    200
    An open source software implementation of the Java Servlet and JavaServer Pages technologies
    12.5K
    8.9K
    + 1
    200
    PROS OF APACHE TOMCAT
    • 79
      Easy
    • 72
      Java
    • 48
      Popular
    • 1
      Spring web
    CONS OF APACHE TOMCAT
      Be the first to leave a con

      related Apache Tomcat posts

      Остап Комплікевич

      I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.

      See more

      Java Spring JUnit

      Apache HTTP Server Apache Tomcat

      MySQL

      See more
      Jetty logo

      Jetty

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

      related Jetty posts

      Grizzly logo

      Grizzly

      8
      13
      0
      A framework for building scalable server applications
      8
      13
      + 1
      0
      PROS OF GRIZZLY
        Be the first to leave a pro
        CONS OF GRIZZLY
          Be the first to leave a con

          related Grizzly posts

          Netty logo

          Netty

          207
          302
          13
          Asynchronous event-driven network application framework
          207
          302
          + 1
          13
          PROS OF NETTY
          • 7
            High Performance
          • 3
            Easy to use
          • 3
            Just like it
          CONS OF NETTY
          • 1
            Limited resources to learn from

          related Netty posts

          Spring Boot logo

          Spring Boot

          17.7K
          15.7K
          913
          Create Spring-powered, production-grade applications and services with absolute minimum fuss
          17.7K
          15.7K
          + 1
          913
          PROS OF SPRING BOOT
          • 134
            Powerful and handy
          • 127
            Easy setup
          • 118
            Java
          • 86
            Spring
          • 82
            Fast
          • 42
            Extensible
          • 34
            Lots of "off the shelf" functionalities
          • 29
            Cloud Solid
          • 23
            Caches well
          • 21
            Many receipes around for obscure features
          • 20
            Productive
          • 20
            Modular
          • 19
            Spring ecosystem is great
          • 19
            Integrations with most other Java frameworks
          • 18
            Fast Performance With Microservices
          • 17
            Auto-configuration
          • 16
            Community
          • 13
            One-stop shop
          • 13
            Easy setup, Community Support, Solid for ERP apps
          • 12
            Cross-platform
          • 12
            Easy to parallelize
          • 11
            Easy setup, good for build erp systems, well documented
          • 11
            Powerful 3rd party libraries and frameworks
          • 10
            Easy setup, Git Integration
          • 3
            Kotlin
          • 3
            It's so easier to start a project on spring
          CONS OF SPRING BOOT
          • 20
            Heavy weight
          • 17
            Annotation ceremony
          • 10
            Many config files needed
          • 8
            Java
          • 5
            Reactive
          • 4
            Excellent tools for cloud hosting, since 5.x

          related Spring Boot posts

          Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

          Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

          See more
          Praveen Mooli
          Engineering Manager at Taylor and Francis · | 14 upvotes · 2.1M views

          We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

          To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

          To build #Webapps we decided to use Angular 2 with RxJS

          #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

          See more
          NGINX logo

          NGINX

          95.4K
          45.6K
          5.5K
          A high performance free open source web server powering busiest sites on the Internet.
          95.4K
          45.6K
          + 1
          5.5K
          PROS OF NGINX
          • 1.4K
            High-performance http server
          • 896
            Performance
          • 728
            Easy to configure
          • 606
            Open source
          • 529
            Load balancer
          • 286
            Scalability
          • 285
            Free
          • 222
            Web server
          • 173
            Simplicity
          • 134
            Easy setup
          • 29
            Content caching
          • 19
            Web Accelerator
          • 14
            Capability
          • 13
            Fast
          • 11
            Predictability
          • 10
            High-latency
          • 7
            Reverse Proxy
          • 6
            Supports http/2
          • 4
            The best of them
          • 4
            Lots of Modules
          • 4
            Enterprise version
          • 4
            Great Community
          • 3
            High perfomance proxy server
          • 3
            Streaming media
          • 3
            Embedded Lua scripting
          • 3
            Reversy Proxy
          • 3
            Streaming media delivery
          • 2
            Fast and easy to set up
          • 2
            Lightweight
          • 2
            Slim
          • 2
            saltstack
          • 1
            Virtual hosting
          • 1
            Blash
          • 1
            GRPC-Web
          • 1
            Ingress controller
          • 1
            Narrow focus. Easy to configure. Fast
          • 1
            Along with Redis Cache its the Most superior
          • 0
            A
          CONS OF NGINX
          • 8
            Advanced features require subscription

          related NGINX posts

          Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

          We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

          See more
          Gabriel Pa
          Shared insights
          on
          TraefikTraefikNGINXNGINX
          at

          We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

          We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

          The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

          See more
          Apache HTTP Server logo

          Apache HTTP Server

          59.6K
          18.4K
          1.4K
          The most popular web server on the Internet since April 1996
          59.6K
          18.4K
          + 1
          1.4K
          PROS OF APACHE HTTP SERVER
          • 477
            Web server
          • 305
            Most widely-used web server
          • 218
            Virtual hosting
          • 148
            Fast
          • 138
            Ssl support
          • 45
            Since 1996
          • 28
            Asynchronous
          • 5
            Robust
          • 4
            Proven over many years
          • 1
            Mature
          • 1
            Perfect Support
          • 1
            Perfomance
          • 0
            Many available modules
          • 0
            Many available modules
          CONS OF APACHE HTTP SERVER
          • 2
            Hard to set up

          related Apache HTTP Server posts

          Tim Abbott
          Shared insights
          on
          NGINXNGINXApache HTTP ServerApache HTTP Server
          at

          We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

          Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

          See more
          Marcel Kornegoor
          Shared insights
          on
          NGINXNGINXApache HTTP ServerApache HTTP Server

          nginx or Apache HTTP Server that's the question. The best choice depends on what it needs to serve. In general, Nginx performs better with static content, where Apache and Nginx score roughly the same when it comes to dynamic content. Since most webpages and web-applications use both static and dynamic content, a combination of both platforms may be the best solution.

          Since both webservers are easy to deploy and free to use, setting up a performance or feature comparison test is no big deal. This way you can see what solutions suits your application or content best. Don't forget to look at other aspects, like security, back-end compatibility (easy of integration) and manageability, as well.

          A reasonably good comparison between the two can be found in the link below.

          See more