WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
$88.50
per month
JBoss SOA Platform
Score 9.0 out of 10
N/A
Red Hat JBoss SOA Platform drives business execution, responsiveness, and flexibility in an open platform. It delivers what the vendor describes as an easy-to-consume service-oriented architecture (SOA) integration suite that lets users build, deploy, integrate, and orchestrate applications and services.
IBM support is better than Oracle, from past experience. Weblogic and WebSphere Application Server are somewhat similar versus the open source JBOSS. For many applications we had selected WAS to have a supported platform and used some of the competitors in other various use …
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
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.
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.
Ease of use in terms of deployment, give simple interface to do simple stuff like Tomcat, JBoss or GlassFish.
Takes long time to start the server.
The Liferay wars need to be decorated and then deployed. Perhaps we could simplify that.
Some of the concepts are good for complexity that WAS can handle but could be simplified and better documented, like concepts of well and profile, context, etc.
A Liferay war file created using Liferay Developer studio runs fine in Tomcat, however that may not run in WAS 7.x because it needs to be decorated. I had one war for a Liferay portlet with a simple cron job, and had hard time running to WAS server. It was running on the latest free download done on my friends m/c. Other times I have seen that there are issues running a war file that runs on Tomcat but runs on WAS after lot of customization for WAS.
The corporations like this however, the product may need better vibrant community of users where issues can be discussed.
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
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
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.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its processing was much faster than Cleo Integration Cloud
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.
Continuous uptime of the business applications we manage
It's now much simpler for me to build and deploy cloud-native applications.
Because it can offload for me management and maintenance of the application server to IBM I can focus on the development, deployment and testing of the applications which is more important
