Payara Platform vs. The Competition

Payara Platform

Can the Payara Platform solve the problems you’re having with your current application server? Find your runtime below and learn how the Payara Platform overcomes your challenges.

Payara Server Enterprise is the best application platform for production Jakarta EE (Java EE)  apps.

Learn More

Payara Micro Enterprise is the lightweight middleware platform of choice for containerized Jakarta EE (Java EE)  microservices deployments.

Learn More

Compare Your App Server to Payara Platform

View the following comparison tables and infographics to see how the features and benefits of Payara Server and Payara Micro compare to other application servers.

GlassFish

Running GlassFish and worried about the lack of support, infrequent application server releases, and lack of bug fixes? Migrate to Payara Server.

Compare GlassFish

WebLogic

Migrating from Oracle WebLogic Server to Payara Server can be a simple and straightforward process because both servers rely on the Java EE specifications.

Compare WebLogic

TomEE

Using TomEE but need more frequent releases, greater security, and automatic clustering? Migrate to Payara Server.

Compare TomEE

JBoss EAP

Tired of paying extra for data grid (caching) with JBoss? Want a monthly component upgrade schedule, Slow SQL Logging, Health Check Service, and included OAuth2 / OpenID Connect Support at no additional cost? Migrate to Payara Server.

Compare JBoss

Tomcat

Using Tomcat for simple web applications and wish microservices features were built-in? Wish you had access to knowledgeable support services? Migrate to Payara Server.

Compare Tomcat

WildFly

Wish you had a supported application server with regular releases and component upgrades? Need a health check service, slow SQL logging, additional notification channels monitoring with an integrated monitoring console? Migrate from WildFly 20 to Payara Server.

Compare WildFly

Quarkus

Quarkus focuses on fast start up time but not without some costs. If you need a more mature ecosystem that performs well under load and is not coupled with the downsides of GraalVM. Consider migrating to Payara Micro.

Compare Quarkus

Helidon

If you need support for older JDK versions, Jakarta EE compatibility, automatic clustering or production support then you may want to consider migrating to Payara Micro.

Compare Helidon

WebSphere

If you prefer an Open Source license, need Data Grid (caching), and want the ability to use admin command recording and auditing, migrate to Payara Server Enterprise.

Compare WebSphere

Contact UsMigration Resources

GlassFish vs. Payara Server

FeatureGlassFish 7.0.11Payara Server Enterprise 6.9.0
LicenseOpen SourceOpen Source
Release FrequencyMonthly (Source)Monthly
Security FixesMonthly
  • Instant emergency and backported fixes for Payara Enterprise customers
  • As soon as possible for community
Production SupportNot a product (OmniFish and ManageCat offer support) (Source)Yes
Migration & Project SupportNoYes
Component UpgradesAs neededAs needed
Supported IDEs
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • Visual Studio Code
Caching ToolsNoJCache, Domain Data Grid, Payara Scales (additional cost)
Automatic ClusteringNoYes (via Hazelcast)
Asadmin Command RecorderNoYes
Slow SQL LoggingNoYes
Health Check ServiceNoYes
Request TracingNoYes
Monitoring LoggingNoYes
Custom NotifiersNoYes
Microservices DistributionNoYes (Payara Micro)
MicroProfile SupportMinimal (Source)Yes
Docker SupportCommunity providedOfficial images
HTTP & HTTPS Port Auto-bindingNoYes (Payara Micro only)
Generate Uber JARNoYes (Payara Micro only)
Production-tuned Domain TemplateNoYes
Upgrade ToolNoYes (Watch demo.)
Jakarta EE CompatibleYesYes
Runs on JDK 11YesYes
Embedded Data GridNoYes (Domain Data Grid)

GlassFish to Payara Server Migration

The Migration & Project Support that I’ve received from the Payara Engineers has been exceptional thus far. They helped me pinpoint an issue that we’ve been having and also referenced me to the GitHub page where another user had a similar issue. Furthermore, they have back-tested the issue that we’d experienced and figured out what the latest version is that we can upgrade to, where our existing code-base would still work. In the meantime, while the Support Team was busy investigating the issue, we migrated from GlassFish to Payara Server on one of our production servers. Thus far, the transition has been seamless and exciting.

Mark Bekker, HelloGroup

Overall the migration from GlassFish 3 over to Payara Platform 5 was a straightforward process. There was no need for major code rewrites. Setar invested in the Migration & Project Support for help during the migration process and Payara’s engineering team was clearly knowledgeable when answering the support tickets.

I’m enjoying the fact that all my knowledge about GlassFish can now be applied to the usage of Payara Platform. There is no need to put time aside to learn about a different technology, our team can start working with Payara Platform hands on straight away.

Enrick Lopez, lead developer at SETAR NV

WebLogic vs. Payara Server

FeatureOracle® WebLogic Server 14c (14.1.1.0.0.)Payara® Server Enterprise 6.9.0
LicenseProprietaryOpen Source with EULA
Release FrequencyIrregularMonthly
Production SupportYesYes
Component UpgradesIrregularMonthly
Supported IDEsEclipse® / Netbeans® / IntelliJ® IDE / JDeveloper®Eclipse / Netbeans / IntelliJ IDE / VSCode
Support for Java EE Applications
  • Java EE 8 and Jakarta EE 8
  • Java SE 8 and 11 Support
  • GraalVM EE Support
  • Java EE 10
  • Jakarta EE 10
Caching ToolsOracle Coherence / JCacheHazelcast: JCache, Domain Data Grid, Payara Scales (additional cost)
ClusteringEvery node runs same appsYes (via Hazelcast)
Every node runs same app or fine grained assignment
Scripting toolWSLTasadmin
Scripting extensionsPython scriptsOS / BASH scripts
Asadmin command recorderYesYes
Deployment FlexibilityDeployment plan (XML based)Variables (System, environment, MicroProfile config values)
Notification Channels Monitoring
  • JMX Beans
  • Log files
  • SMTP
  • SNMP
  • JMS
  • JMX Beans
  • Log files
  • SMTP
  • SNMP
  • JMS
  • CDI
  • Slack
  • New Relic
  • Datadog
Custom NotifiersNoYes
Slow SQL LoggingNoYes
Health Check ServiceYesYes
Request TracingJAX-RS (Jersey) onlyJAX-RS, CDI, EJB, Servlet, ...
OAuth2/OpenId Connect supportRequires Fusion Middleware or custom devNatively supported (through Security API)
Microservices DistributionNo - Helidon for microservicesYes, Payara® Micro
MicroProfile SupportNoYes
Uber-jar and Hollow JarNoYes
Docker SupportYesYes
Cloud Providers SupportOracle Cloud, Amazon, Microsoft Azure™, JelasticMicrosoft Azure, Jelastic, Amazon, Oracle Cloud
Zero Deployment downtimeParallel versions with gradual switchParallel versions with one time switch
Upgrade ToolYesYes
JDK SupportJDk 11Yes (through Azul® JVM), JDK 11
Microsoft and Microsoft Azure are registered trademarks of Microsoft.
Eclipse and MicroProfile are trademarks of Eclipse Foundation, Inc.
Oracle, NetBeans, JDeveloper, and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
IntelliJ® is a registered trademark owned by Jetbrains s.r.o.
Hazelcast is a trademark of Hazelcast, Inc. All other trademarks used herein are the property of their respective owners.
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. Docker, Inc. and other parties may also have trademark rights in other terms used herein.
Azul Systems is a registered trademarks of Azul Systems Inc.

WebLogic to Payara Server Migration

We migrated the backend of the product we built for our client from WebLogic to Payara Server with great success. Payara Server has a much more modern feature-set and feel, gets you up and running quicker and we saved a lot of time configuring the server compared to WebLogic. Several things that were a big hassle to configure with WebLogic worked out of the box with Payara Server, Bean Validation being a prime example of this. We are now looking to the future and planning a move towards a more microservices oriented architecture with Payara Micro in mind. I would recommend both Payara Server and Payara Micro to anybody who values consistency, stability and productivity for their application development and deployment.

Daniel Löfquist, HiQ

TomEE vs. Payara Server

FeatureTomEE 9Payara Server Enterprise 6.9.0
LicenseOpen SourceOpen Source with EULA
Release frequencyIrregular (about 2 a year)Monthly
Patch releasesIrregularIrregular
Security fixesInfrequent
  • Instant emergency and backported fixes for Payara Enterprise customers
  • As soon as possible for community
Production supportYes (Tomitribe)Yes
Component Upgrades (e.g. Tyrus, Mojarra)IrregularMonthly
Supported IDEs
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • VS Code
Caching toolsJCacheHazelcast, JCache, Domain Data Grid, Payara Scales (additional cost)
Automatic ClusteringNo, manual via Tomcat
Cluster
Yes, (via Hazelcast)
Command line toolYes - Apache TomEE-CLIYes - Asadmin
Web ConsoleBasic (From Tomcat)Almost all commands supported
Asadmin command recorderNoYes
Slow SQL loggingNoYes
Healthcheck serviceNoYes
Request tracingNoYes
Monitoring loggingNoYes
Microservices distributionYes, TomEE
MicroProfile
Yes (Payara Micro)
MicroProfile supportMicroProfile 5MicroProfile 6.1
Docker supportYesYes
Generate Uber JARYesYes (Payara Micro only)
Production-tuned domain templateNoYes
EE StandardJakarta EE 9Jakarta EE 10
Jakarta EE CompatibleYesYes
Upgrade ToolYesYes
Runs on JDK 11YesYes (through Azul JVM)

TomEE to Payara Server Migration

JBoss EAP vs. Payara Server

FeatureJBoss EAP 7.4Payara Server Enterprise 6.9.0
LicenseOpen Source with EULAOpen Source with EULA
Release FrequencyBimonthly (Source)Monthly
Production SupportYesYes
Component UpgradesFrequentMonthly
Supported IDEs
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • Visual Studio Code
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • Visual Studio Code
Jakarta EE 10 CompatibleNo (Source)Yes
Data Grid (Caching)Infinispan (additional cost)Hazelcast / JCache
ClusteringEvery node runs the same app or fine grained assignment. Automatic clustering over multicast. (Source)Every node runs the same app or fine grained assignment. Automatic clustering over multicast.
Scripting Tooljboss-cli.shasadmin
Admin Command Recording and AuditingYesYes
Deployment FlexibilityVariable (System, environment, external file, MicroProfile config)Variables (System, environment, MicroProfile config)
Notification Channels Monitoring
  • CDI
  • JMS
  • Log Files
  • JMS Beans
  • Log Files
  • SMTP
  • SNMP
  • JMS
  • CDI
  • Slack
  • New Relic
  • Datadog
Custom NotifiersNoYes
Slow SQL LoggingNoYes
Health Check ServiceNoYes
Request TracingYes (JAX-RS, CDI)Yes (JAX-RS, CDI, EJB, Servlet)
OAuth2 / OpenId Connect SupportYes, through Red Hat Single Sign-On (additional cost)Natively Supported (through Security API)
Microservices EditionNo (the WildFly Bootable JAR Maven Plugin can be used to build a Bootable JAR, packaging server and application) (Source)Payara Micro
MicroProfile SupportPartialYes
Docker SupportYesYes, also with container automation through Payara Docker Nodes
Kubernetes SupportYesYes
Cloud Providers SupportMicrosoft Azure, Amazon, Google, OpenShift, and moreMicrosoft Azure, Google, Jelastic, Amazon, Oracle Cloud, and more
Zero Deployment DowntimeNo (Source)Parallel versions with one-time switch
Upgrade ToolYesYes
Bundled JDK SupportYes - RHEL and Windows onlyYes - Linux & Windows
Easy Migration from Community to EnterpriseWildFly migration to JBoss EAP Possible - Challenging (Source)Yes - Payara Platform to Payara Platform Enterprise -Simple migration
Integrated Monitoring ConsoleYes (additional cost)Yes

JBoss EAP to Payara Server Migration

Tomcat vs. Payara Server

FeatureTomcat 10.1Payara Server Enterprise 6.9.0
LicenseOpen Source/Apache-2.0 LicensedOpen Source with EULA
Release frequencyMonthlyMonthly
Patch releasesIrregularIrregular
Security fixesIrregular but frequent
  • Instant emergency and backported fixes for Payara Enterprise customers
  • As soon as possible for community
Production supportYes (Tomitribe)Yes
Component Upgrades (e.g. Tyrus, Mojarra)MonthlyMonthly
Supported IDEs
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • Eclipse
  • Netbeans
  • IntelliJ IDEA
  • VS Code
Caching toolsJCacheHazelcast, JCache, Domain Data Grid, Payara Scales (additional cost)
Automatic ClusteringNo, manual via Tomcat
Cluster
Yes, (via Hazelcast)
Command line toolYesYes - Asadmin
Web ConsoleYesAlmost all commands supported
Asadmin command recorderNoYes
Slow SQL loggingNoYes
Healthcheck serviceHealthcheck valveYes
Request tracingNoYes
Monitoring loggingNoYes
Microservices distributionNoYes (Payara Micro)
MicroProfile supportNoMicroProfile 6.1
Docker supportYesYes
Generate Uber JARYesYes (Payara Micro only)
Production-tuned domain templateNoYes
EE StandardJakarta EE 10Jakarta EE 10
Jakarta EE CompatibleYesYes
Upgrade ToolYesYes
Runs on JDK 11YesYes (through Azul JVM)

WildFly vs. Payara Server

FeatureWildFly 30Payara Server Community 6.2023.12Payara Server Enterprise 6.9.0
LicenseOpen Source (Source)Open SourceOpen Source with EULA
Release FrequencyQuarterly (Source)MonthlyMonthly
Production SupportNoNoYes
Component UpgradesQuarterlyMonthlyMonthly
Supported IDEs
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • Red Hat Development Suite
  • Visual Studio Code
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • Visual Studio Code
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • Visual Studio Code
Jakarta EE 10 CompatibleYesYesYes
Caching ToolsInfinispanHazelcastHazelcast
ClusteringEvery node runs same app or fine grained assignment.Every node runs same app or fine grained assignment.Every node runs same app or fine grained assignment.
Data Encryption in a ClusterYesYes Yes
Web UI AdministrationYesYesYes
Scripting Tooljboss-cli.sh asadminasadmin
Admin Command RecordingYesYesYes
Auditing Management OperationsYesYesYes
Auditing Security EventsYesYesYes
Integrated Certificate ManagementNoNoYes
Deployment FlexibilityVariables (System, environment, external file, MicroProfile config) Variables (System, environment, MicroProfile config) Variables (System, environment, MicroProfile config)
Notification Channels Monitoring
  • CDI
  • JMS Beans
  • Log Files
  • JMS Beans
  • Log Files
  • SMTP
  • SNMP
  • JMS
  • CDI
  • Slack
  • New Relic
  • Datadog
  • JMS Beans
  • Log Files
  • SMTP
  • SNMP
  • JMS
  • CDI
  • Slack
  • New Relic
  • Datadog
Custom NotifiersNoYesYes
Slow SQL LoggingNoYesYes
Health Check ServiceYes via MicroProfile HealthYesYes
Request TracingYes (JAX-RS, CDI)Yes (JAX-RS, CDI, EJB, Servlet, JAX-WS, JMS) Yes (JAX-RS, CDI, EJB, Servlet, JAX-WS, JMS)
OAuth2 / OpenId Connect SupportYes, through Elytron subsystem Natively Supported (through Security API) Natively Supported (through Security API)
Remote EJB over HTTPYesYes (partial)Yes (partial)
Microservice DistributionNo (the WildFly Bootable JAR Maven Plugin can be used to build a Bootable JAR, packaging server and application) (Source)Payara MicroPayara Micro
MicroProfile SupportYesYesYes
Docker SupportYesYes, also with container automation through Payara Docker Nodes Yes, also with container automation through Payara Docker Nodes
Kubernetes SupportYesYesYes
Cloud Providers SupportMicrosoft Azure, Amazon, Google, Openshift, and more Microsoft Azure, Jelastic, Amazon, Oracle Cloud, and more Microsoft Azure, Jelastic, Amazon, Oracle Cloud, and more
Zero Deployment DowntimeNoSwitch between pre-deployed versions; Rolling upgrade in a cluster Switch between pre-deployed versions; Rolling upgrade in a cluster
Hot DeploymentNoYes for NetBeans IDE, Maven, Gradle, support for other IDEs coming soonYes for NetBeans IDE, Maven, Gradle, support for other IDEs coming soon
Upgrade ToolYesNo Yes
JDK 21 SupportPartialYesYes
Bundled JDK SupportYes - RHEL and Windows Yes - Linux and Windows Yes - Linux and Windows
Migration from Community to Enterprise editionChallenging (Wildfly to JBoss EAP migration) (Source)Simple and supportedSimple and supported
Integrated Monitoring ConsoleNoYesYes

WildFly to Payara Server Migration

Quarkus Vs Payara Micro

FeatureQuarkus 3.6.3Payara Micro Enterprise 6.9.0
LicenseApache License 2.0 (Source)
Open Source with EULA
Release FrequencyRegularMonthly
Production SupportYes (Only in combination with OpenShift or Enterprise Linux subscriptions)Yes
Standards SupportMicroProfile, Partial Jakarta EE (Source)
MicroProfile, Jakarta EE 10 Web Profile
Support ForVert.x, MP Reactive Messaging, MP GraphQL, JPA, JMS ClientJBatch, Jakarta EE Concurrency, JMS client, Kafka connectivity
Designed ForKubernetes
Microservices, Kubernetes, general applications
Project CreationMaven archetype (Source)
Maven and Gradle archetypes
ClusteringAvailable through Infinispan integration (Source)Automatic clustering in many environments including bare metal and Kubernetes
Request TracingMicroProfile OpenTracing, OpenTelemetry TraceMicroProfile OpenTracing Servlet, CDI
Tracing ToolsJaeger, OpenZipkinJaeger, OpenZipkin
NotifiersNone
  • Log files
  • SMTP
  • SNMP
  • CDI
  • Slack
  • New Relic
  • Datadog
  • Discord
  • Teams
  • Java Flight Recorder
  • XMPP
Supported JVMsJDK 11+, Graal VM Native compilation (Source)Support and security updates for Java 11, 17 and beyond; and ARM-based JVMs

Helidon Vs Payara Micro

FeatureHelidon 4Payara Micro Enterprise 6.9.0
LicenseApache License 2.0Open Source with EULA
Release FrequencyRegularMonthly
Production SupportYes (Only in combination with WebLogic or Coherence)Yes
Standards SupportMicroProfile, Partial Jakarta EEMicroProfile, Jakarta EE 10 Web Profile
Support ForMP Reactive Messaging, MP GraphQL, gRPC, JPAJBatch, Jakarta EE Concurrency, JMS client, Kafka connectivity
Supported IDEs
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • VSCode
  • Eclipse
  • NetBeans
  • IntelliJ IDEA
  • VSCode
Designed ForMicroservicesMicroservices, general applications
Project CreationHelidon CLI, Maven, and Gradle archetypesMaven and Gradle archetypes
ClusteringNoneAutomatic clustering in many environments including bare metal and Kubernetes
ConfigurationYAML fileAsadmin commands
Request TracingJersey, MicroProfile OpenTracingMicroProfile OpenTracing, Servlet, CDI
Tracing ToolsJaeger, OpenZipkinJaeger, OpenZipkin
NotifiersNone
  • Log files
  • SMTP
  • SNMP
  • CDI
  • Slack
  • New Relic
  • Datadog
Supported JVMsJDK 21+, Graal VM Native compilation (Source)
Support and security updates for Java 11, 17 and beyond; and ARM-based JVMs

WebSphere VS. Payara Server Enterprise

WebSphere 9.0.5WebSphere Liberty 23.0.0Payara Server Enterprise 6.9.0
LicenseProprietaryProprietaryOpen Source with EULA
Release FrequencyIrregularMonthlyMonthly
Production SupportYesYesYes
Supported IDEsEclipse IDE, VS CodeEclipse IDE, VS CodeEclipse IDE, NetBeans, IntelliJ IDE, VS Code
Jakarta EE 8 CompatibleYesYesYes
MicroProfile SupportPartialYesYes
Microservices EditionNoYes (Liberty is positioned as Microservices only)Yes (Payara Micro)
Data Grid (Caching)Separate product with additional costNoYes, included
ClusteringSeparate product with additional costYesYes, included
Scripting ToolWsadmin and jython scriptsWsadmin and jython scriptsasadmin
Admin Command Recording and AuditingNoNoYes
Deployment FlexibilityVariables (Environment, external files, WebSphere variables)Variables (Environment, WebSphere variables, MicroProfile config)Variables (System, Environment, MicroProfile config)
Notification Channels Monitoring,ul>
  • JMS Beans
  • SMTP
  • Google Cloud Messaging
  • Apple Push Notifications
    • JMS Beans
    • SMTP
    • JS Beans
    • Log Files
    • SMTP
    • SNMP
    • JMS
    • CDI
    • Slack
    • New Relic
    • Datadog
    • Teams Channels
      Custom NotifiersNoNoYes
      Back to top