We performed a comparison between IBM WebSphere Message Broker and webMethods Integration Server 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."The transactions and message queuing are the most valuable features of the solution."
"It has many interfaces and you can connect to any backend source that has another format, and convert it to the desired format."
"Message Broker is valuable because most of the applications are using MQ. Even in my current engagement, the few applications which I audit to onboard the bank are using MQ."
"The documentation, performance, stability and scalability of the tool are valuable."
"Straightforward development and deployment."
"Integration and mapping are easy, which is a major advantage."
"The most valuable feature of IBM WebSphere Message Broker is the ability to facilitate communication with legacy systems, offering a multitude of great capabilities. For example, if there is a mainframe system in place with a web service serving as the front end. In that case, the solution enables efficient protocol transformations to convert all request payloads into a format that the legacy systems can accept, rendering the integration and transformation processes seamless and highly effective."
"It is a scalable solution...The setup is easy."
"webMethods Integration Server is an easy-to-use solution and does not require a lot of coding."
"From a user perspective, the feature which I like the most about Integration Server is its designer."
"We can arrange data caching and look at the solid state. Also, the API gateway is a very good component that can handle relevant cachings and integrations, as well as and also load permitting."
"How simple it is to create new solutions."
"They are the building blocks of EAI in SAG products, and they offer a very good platform."
"Operationally, I consider the solution to be quite good."
"Segregation of deployment for the environments is the most valuable feature of the solution."
"We needed a tool that was able to orchestrate and help us configure our APIs so that we could maintain and see the heartbeat, traffic, trends, etc."
"Stability and pricing are areas with shortcomings that need improvement."
"The user interface is designed mainly for experts, much in the way a BPM or another integration tool is."
"The images and size of the containers are too big and I think that they should be more lightweight."
"Technical support is good but they could have a better response time."
"There is some lag in the GUI. There have been some performance issues and maybe it's because of the application data."
"Today I probably wouldn't go for Message Broker because of the cost structure, support, and the whole ecosystem around IBM."
"The solution can add container engines such as docker."
"It is currently a weighty product."
"t doesn't represent OOP very well, just a method and proprietary interface called IData."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"Business monitoring (BAM) needs improvement because the analytics and prediction module very often has performance problems."
"The initial setup of the webMethods Integration Server is not easy but it gets easier once you know it. It is tiresome but not difficult."
"webMethods Integration Server could improve on the version control. I'm not sure if Web Method has some kind of inbuilt integration with Bitbucket or GitHub or some kind of version control system. However, that's one area where they can improve."
"It could be more user-friendly."
"This product has too many gaps. You find them after update installations. This should be covered by automatic testing."
More webMethods Integration Server Pricing and Cost Advice →
IBM WebSphere Message Broker is ranked 8th in Enterprise Service Bus (ESB) with 11 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. IBM WebSphere Message Broker is rated 7.8, while webMethods Integration Server is rated 8.0. The top reviewer of IBM WebSphere Message Broker writes "For new applications that are being onboarded, we engage this tool so the data can flow as required but there's some lag in the GUI". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". IBM WebSphere Message Broker is most compared with IBM Integration Bus, Mule ESB, IBM DataPower Gateway, IBM BPM and Red Hat Fuse, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Azure Data Factory. See our IBM WebSphere Message Broker vs. webMethods Integration Server 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.
