Payara Server vs. Red Hat JBoss Enterprise Application Platform

- If the application is very large then the Payara server is suitable and in the case of a small application, we can choose Micro Payara. - Micro payara is very well suited for microservice architecture. - Fully Jakarta compliance. - Very good performance.

Incentivized

JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.

Incentivized

• Small memory footprint.
• Fully JEE compliant with an exceptional administration console.
• Very good performance.

Incentivized

• MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
• Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
• Supports deployment in on-premise, virtual and hybrid cloud environments.

Incentivized

• Issues that are logged in Payara GitHub forum need to address on time, but it keeps on postponing fixing those issues.

Incentivized

• Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks.
• JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc.

Incentivized

We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop

Incentivized

As mentioned before it has an amazing configuration console. You can practically do anything from there and even update the program or install new features on the fly.

Incentivized

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

As mentioned before, its performance capabilities were one of the reasons we used them. It interacts with mass mail software and we see no performance impact. It handles everything pretty well and pretty fast.

Incentivized

Usually, Red Hat JBoss Enterprise Application Platform is good at performance and well suited for high traffic Java EE-based applications, but we have faced hard times performance tuning it for our specific needs. The product would be nicer if they would add a performance diagnostic and recommendations feature to it.

Incentivized

Fast response.

Incentivized

- As I said before, Payara has full Jakarta compliance and provide up-to-date technology stack upgrade. - Easy to install and upgrade. - Very less configuration setting. - Default ready-to-use production domain is available, which can be spun up to use in production.

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

• Can host multiple application on single VM.
• Helps managed service team reduces their time on installation and up-gradation ( upgrading it to a new Payara server is very simple).
• We can opt for Payara or Micro Payara based on the application size.

Incentivized

• Improved delivery timelines due to easy out of the box setup.
• It is a cheap subscription-based/open-source Java EE-based application server. This reduces the overall cost of delivery.

Incentivized