Alternatives to Payara logo

Alternatives to Payara

GlassFish, Wildfly, Jetty, Apache Tomcat, and JBoss are the most popular alternatives and competitors to Payara.
43
69
+ 1
0

What is Payara and what are its top alternatives?

It Server is a drop in replacement for GlassFish Server Open Source Edition with quarterly releases containing enhancements, bug fixes and patches.
Payara is a tool in the Web Servers category of a tech stack.
Payara is an open source tool with 862 GitHub stars and 295 GitHub forks. Here’s a link to Payara's open source repository on GitHub

Top Alternatives to Payara

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

  • Wildfly
    Wildfly

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

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

  • Apache Tomcat
    Apache Tomcat

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

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

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

Payara alternatives & related posts

GlassFish logo

GlassFish

518
109
0
The Open Source Java EE Reference Implementation
518
109
+ 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

      Wildfly logo

      Wildfly

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

        related Wildfly posts

        Jetty logo

        Jetty

        497
        304
        43
        An open-source project providing an HTTP server, HTTP client, and javax.servlet container
        497
        304
        + 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

        Apache Tomcat logo

        Apache Tomcat

        15.9K
        11.8K
        201
        An open source software implementation of the Java Servlet and JavaServer Pages technologies
        15.9K
        11.8K
        + 1
        201
        PROS OF APACHE TOMCAT
        • 79
          Easy
        • 72
          Java
        • 49
          Popular
        • 1
          Spring web
        CONS OF APACHE TOMCAT
        • 2
          Blocking - each http request block a thread
        • 1
          Easy to set up

        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
        JBoss logo

        JBoss

        432
        237
        0
        An open source Java EE-based application server
        432
        237
        + 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

            Spring Boot logo

            Spring Boot

            24.3K
            22K
            1K
            Create Spring-powered, production-grade applications and services with absolute minimum fuss
            24.3K
            22K
            + 1
            1K
            PROS OF SPRING BOOT
            • 145
              Powerful and handy
            • 133
              Easy setup
            • 125
              Java
            • 90
              Spring
            • 85
              Fast
            • 46
              Extensible
            • 37
              Lots of "off the shelf" functionalities
            • 32
              Cloud Solid
            • 26
              Caches well
            • 24
              Many receipes around for obscure features
            • 24
              Productive
            • 23
              Modular
            • 23
              Integrations with most other Java frameworks
            • 22
              Spring ecosystem is great
            • 21
              Fast Performance With Microservices
            • 20
              Auto-configuration
            • 18
              Community
            • 17
              Easy setup, Community Support, Solid for ERP apps
            • 15
              One-stop shop
            • 14
              Cross-platform
            • 14
              Easy to parallelize
            • 13
              Powerful 3rd party libraries and frameworks
            • 13
              Easy setup, good for build erp systems, well documented
            • 12
              Easy setup, Git Integration
            • 5
              It's so easier to start a project on spring
            • 4
              Kotlin
            • 1
              The ability to integrate with the open source ecosystem
            • 1
              Microservice and Reactive Programming
            CONS OF SPRING BOOT
            • 23
              Heavy weight
            • 18
              Annotation ceremony
            • 13
              Java
            • 11
              Many config files needed
            • 5
              Reactive
            • 4
              Excellent tools for cloud hosting, since 5.x

            related Spring Boot posts

            Praveen Mooli
            Engineering Manager at Taylor and Francis · | 18 upvotes · 3.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

            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
            NGINX logo

            NGINX

            110.6K
            58K
            5.5K
            A high performance free open source web server powering busiest sites on the Internet.
            110.6K
            58K
            + 1
            5.5K
            PROS OF NGINX
            • 1.4K
              High-performance http server
            • 893
              Performance
            • 729
              Easy to configure
            • 607
              Open source
            • 530
              Load balancer
            • 288
              Free
            • 288
              Scalability
            • 225
              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
              Reversy Proxy
            • 3
              Streaming media delivery
            • 3
              Streaming media
            • 3
              Embedded Lua scripting
            • 2
              GRPC-Web
            • 2
              Blash
            • 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
            • 9
              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

            Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

            See more
            Apache HTTP Server logo

            Apache HTTP Server

            63.7K
            22K
            1.4K
            Open-source HTTP server for modern operating systems including UNIX and Windows
            63.7K
            22K
            + 1
            1.4K
            PROS OF APACHE HTTP SERVER
            • 479
              Web server
            • 305
              Most widely-used web server
            • 218
              Virtual hosting
            • 148
              Fast
            • 138
              Ssl support
            • 44
              Since 1996
            • 28
              Asynchronous
            • 5
              Robust
            • 4
              Proven over many years
            • 2
              Perfomance
            • 1
              Mature
            • 1
              Perfect Support
            • 0
              Many available modules
            • 0
              Many available modules
            CONS OF APACHE HTTP SERVER
            • 4
              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