JBoss SOA Platform vs. Payara Server

JBoss Enterprise SOA Platform is great when you are looking at building more or less pure Java applications and SOA micro-services that may integrate with multiple external data sources. It is less useful when you are looking to build simple SOA applications that are simple in nature since the overhead associated with deploying as well as learning BPEL.

Incentivized

- 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 is open source so the cost overhead to deploy and build application is very low.
• JBoss Enterprise SOA Platform and its parent Redhat are reputed and well adapted in the industry so it is easy to find best practices documentation for complex deployments of JBoss middleware.

Incentivized

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

Incentivized

• JBoss Enterprise SOA Platform is dependent and build for JEE/Java application so using a different programming paradigm will be much harder.
• There is still a learning curve to get familiar with BPEL making it harder to get an SOA micro-service up and running compared to a fully cloud-based service

Incentivized

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

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

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

Redhat support generally is great and that is true for the JBoss Enterprise SOA Platform as well. Even if you do not buy support from Redhat, you can reply on the discussion board and bug fixes via the open-source JBoss without much trouble.

Incentivized

Oracle SOA Suite (Oracle BPM + Oracle BPEL + other components) and IBM WebSphere middleware is most costly and suited if you are already using applications and other middleware components from these vendors. Mulesoft (Salesforce Mule ESB) is best when you need deep integration with one of Salesforce's existing products. JBoss and Apache Web Server are best when you do not want to invest infant CapEx/OpEx on license fee. Apache Web Server based middleware is best for simple SOA applications.

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

• Positive impact on the business by being able to use existing Java/JEE expertise to build and deploy applications and business services.
• Positive ROI due to no license cost for JBoss Enterprise SOA.

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