Payara Server vs. Red Hat JBoss Enterprise Application Platform

Payara Server is recommended for any type of jee and/or Spring application. Unless there are proprietary framework restrictions there is no reason for not using Payara. The pricing model for enterprise support is very nice and I would definitely recommend it. The case where it is least recommended is when you need a separate application server per service. In this case, there might be better options for this job even though I am not very sure and need to test more.

Incentivized

Red Hat JBoss Enterprise Application Platform (JBoss EAP) is well suited for deploying high transaction Java EE based applications. It supports many 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

We run a high traffic B2B application on JBoss and it is very stable. Boot time when restarting services is also fast

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

WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over WebSphere Application Server. Also, JBoss EAP is light weight and requires less server resource

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

• Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
• Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.

Incentivized