IBM DataPower Gateway vs. IBM WebSphere Hybrid Edition vs. WSO2 API Manager

WebSphere DataPower Gateway is really beneficial if you are trying to integrate two or more systems. It provides you with comfort and peace of mind by creating a DMZ zone for the services which are going out of the intranet to hit external clients APIs. It is greatly recommended if you have a very high volume service or API which is being used by a majority of clients because it has a dedicated physical box present which takes care of memory, CPU and all such stuff. So, all your transactions happen at wire-speed.

Incentivized

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.

Incentivized

It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?

Incentivized

• The most obvious thing that DataPower does exceptionally well is security. All the built-in supported security capabilities allow us to isolate most security tasks to DataPower and as a result "protect" down steam services/systems to have to deal with security.
• DataPower is very good at protocol conversion and as it is usually used on the edge allows you to narrow down the protocols used between the companies public and private networks.
• The appliance concept makes maintenance, recovery and, management so much simpler.

Incentivized

• IBM WebSphere Hybrid Edition has done marvelous in building and deploying Java Enterprise applications.
• It also does well in automating deployment and scaling. This has made it easier for our organization to deploy updates to our applications.
• IBM WebSphere Hybrid Edition does well in security by providing features that protect enterprise applications.

Incentivized

• Authentication based on OAuth 2.0 and HTTP Basic Authentication.
• Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
• Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
• Mediation to perform transformation, orchestration etc.

Incentivized

• API security
• WAF improvements
• Security improvements
• REST support
• Kafka support and event streaming

• 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.

Incentivized

• Better QA testing prior to releases rollout
• Better support needed

Incentivized

Cost of the appliance

Incentivized

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.

Incentivized

In terms of usability, it has many advantages over other competitors in terms of integration, as it allows for the optimized creation of integration flows in a very quick and intuitive way from browsers, allowing for granular export and import of work, guaranteeing compatibility between different versions of the product.

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.

Incentivized

Deploys fairly quick enough and like the roll-out update feature decreasing the downtime and also plays well with other integration tools as well.

Incentivized

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!

Incentivized

In his brand DataPower has not competitors, in security, transform and data validations DataPower is better than other products.

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

Incentivized

Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.

Incentivized

• It has really taken our business to the next level. We have expanded and integrated with so many new vendors and for all those integrations DataPower is serving as our security gateway.
• We don't have to depend on any other tool for doing the load balancing of the incoming requests as that is also taken care inside the WebSphere DataPower Gateway box itself, thereby distributing the load equally.
• It has made our platform much more secure, uniform and robust to deal with any kind of incoming message format or threat as well due to its latest security mechanisms and huge processing power.

Incentivized

• 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

Incentivized

• We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
• Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
• Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.

Incentivized