We performed a comparison between IBM DataPower Gateway and IBM Integration Bus based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Service Bus (ESB) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Support for PCA and non-PCA services is valuable."
"You don't have to have a separate DMC proxy because DataPower Gateway is an appliance and will take care of a lot of security features. These include data validations, encryption, as well as XML or any type of scripting or security threats that are present."
"Its initial setup was straightforward."
"It is very easy to set up and configure, even for users with no prior experience."
"The product's most valuable features are AAA policies and security features."
"The scalability of the solution is good."
"The most valuable feature is the security appliance, it's very secure."
"The most valuable features for our business include the ability to monitor and log data transactions and handle multiple request at an enterprise level."
"I use the integration of Kafka and the message flow, which is really good. It is also good for moving any file from one location to another. Using IBM Integration Bus in the data stage is pretty simple. You can see the preview and other things. The MQ server integrated with IBM Integration Bus is really great. I don't have to do a lot of configuration from that side. It is really good."
"It is a stable solution."
"It's easy to develop things, and it's easy to handle."
"Seamlessly integrates your different applications."
"Facilitates communication between parties and legacy systems."
"like the API lead integration, which is more focused, and I also like real-time integration."
"It can be implemented as an enterprise service bus to seamlessly connect all applications within your enterprise."
"One of the most valuable features is App Connect Enterprise makes it possible to deploy it in the OpenShift cluster, which is very good. Overall the solution is very flexible."
"Its support services could be better."
"Additional documentation needs to be provided for complex automations."
"Scripting needs improvement. It's hard for our customers."
"The two biggest issues of this solution are the complexity and the maintenance procedures."
"The programming language is only supported in XSLT and Gateway script."
"They should add features to manage API integrations."
"It is a costly product."
"They should improve the solution's clustering features."
"Licensing is too high. It is quite expensive."
"The interface could be more user-friendly."
"IBM Integration Bus could improve by having a more lightweight installation. Additionally, automation could improve."
"The password settings need improvement."
"Its documentation is currently lacking. We have different environments where we use our configuration services, but we are not able to find documentation about how to deploy the local code to the server and how to set it up on a server level. I would like more documents from IBM that explain which variables should be in your machine while building a project, and when you deploy the code into the server, what should be their values. There are some variable values. I could not find such documentation. While working on a project, I developed the code on a local machine, and while deploying the code to our test environment, I made a couple of mistakes. We had to change some values at the server level, but we couldn't find any documentation regarding this, which made the task difficult."
"The user interface could be improved in a future release."
"Its integration with Cloud Pak components could be better."
"It needs improvement in terms of technical support as well as in terms of integration of data mining. I am not convinced about many things in this solution, such as the conversion of the DFDL or copybook file, which is the conversion from a text file to XML. It is very complex. They should also provide more information about this solution in the IBM Knowledge Center. I can get a lot of information from the IBM Knowledge Center about DataStage, but I don't get that much information about IBM Integration Bus. There is hardly any information even on the internet and various channels such as YouTube. They can provide good step-by-step documentation based on a company's requirements. It would be really helpful. My company is mainly looking for data mining and communicating with multiple servers. IBM Integration Bus is good for communicating with multiple servers, but it needs improvement for XML conversion and data mining. We have a lot of old systems that use XML."
IBM DataPower Gateway is ranked 6th in Enterprise Service Bus (ESB) with 27 reviews while IBM Integration Bus is ranked 1st in Enterprise Service Bus (ESB) with 65 reviews. IBM DataPower Gateway is rated 8.4, while IBM Integration Bus is rated 8.0. The top reviewer of IBM DataPower Gateway writes "Security features meets compliance needs and offers MPGW (Multi-Protocol Gateway) that simplifies integration efforts ". On the other hand, the top reviewer of IBM Integration Bus writes "Scalable solution with efficient integration features". IBM DataPower Gateway is most compared with IBM API Connect, Apigee, Microsoft Azure API Management, Mule ESB and Kong Gateway Enterprise, whereas IBM Integration Bus is most compared with Mule ESB, webMethods Integration Server, Oracle Service Bus, IBM WebSphere Message Broker and Red Hat Fuse. See our IBM DataPower Gateway vs. IBM Integration Bus report.
See our list of best Enterprise Service Bus (ESB) vendors.
We monitor all Enterprise Service Bus (ESB) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.