We performed a comparison between Red Hat Fuse and webMethods Integration Server based on real PeerSpot user reviews.
Find out in this report how the two ESB (Enterprise Service Bus) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's very lightweight. There's no need for any specialized tools in order to deploy any service for Red Hat Fuse."
"Because we have been doing Red Hat Fuse projects for three years, and over time we have matured, we can employ similar use cases and make use of accelerators or templates. It gives us an edge when we deliver these services or APIs quickly."
"The process workflow, where we can orchestrate and design the application by defining different routes, is really useful."
"The support training that comes with the product is amazing."
"One of the features I found most valuable in Red Hat Fuse is that it has a lot of containers so you won't have to worry about load balancing. In the past, there was a cut-off, but nowadays, Red Hat Fuse is moving off of that, so my team is utilizing it the most for load balancing, particularly running goal applications and three to five containers. There's automatic load balancing so you won't have to worry too much. I also found that component-wise, you don't have to do much coding in Red Hat Fuse because everything is configurable, for example, XML-based coding. Coding isn't that difficult. Performance-wise, I also found the solution to be quite good and its processing is quite fast. My team is processing a huge amount of data with the help of Red Hat Fuse."
"The stability has been good."
"The features I found most valuable in Red Hat Fuse are the OSB framework, containerization, and the integration of Apache technologies such as the NQ channel, CXF, etc. These are the features that are very prominent in the solution. Red Hat Fuse also offers flexibility, so it's another valuable characteristic of the solution."
"More than a feature, I would say that the reliability of the platform is the most valuable aspect."
"The stability is good."
"All of the components are very independent but are tied together to give the business value."
"Most of the work in our organization can be more easily done using the tool."
"The synchronous and asynchronous messaging system the solution provides is very good."
"The most valuable feature is stability."
"One [of the most valuable features] is the webMethods Designer. That helps our developers develop on their own. It's very intuitive for design. It helps our developers to speed the development of services for the integrations."
"What I like best about webMethods Integration Server is its portfolio of connectors."
"Ease of implementation and flexibility to hold the business logic are the most valuable features."
"What could be improved in Red Hat Fuse is the deployment process because it's still very heavy. It's containerized, but now with Spring Boot and other microservices-related containers, deployment is still very heavy. Red Hat Fuse still has room for improvement in terms of becoming more containerized and more oriented."
"The web tools need to be updated."
"Our clients would like to see the user interface improved so that it is more user-friendly."
"The pricing model could be adjusted. The price should be lower."
"Red Hat Fuse doesn't have a lot of administrative control like other applications."
"There is definitely a bit of a learning curve."
"Currently, the main point of concern for us is how flexible it is to cater to different requirements. It should be more flexible."
"In the next release, I'd like more stability and more security overall."
"When migration happens from the one release to an upgraded release from Software AG, many of the existing services are deprecated and developers have to put in effort testing and redeveloping some of the services. It would be better that upgrade releases took care to support the lower-level versions of webMethods."
"In terms of scale, I would give it a four out of 10."
"wM SAP Adapter User Guide - Example, like Message Broker setup was unclear, leading to issues during Testing and we had refer the internet forums to understand that there is a Message Broker Cleanup utility and that needs to be setup as well."
"One area that needs improvement is the version upgrade process. Many customers I've worked with encounter challenges when transitioning from their current version, such as x or 9, to a newer version. The process is not smooth, and they must shift their entire website."
"t doesn't represent OOP very well, just a method and proprietary interface called IData."
"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."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"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."
More webMethods Integration Server Pricing and Cost Advice →
Red Hat Fuse is ranked 4th in ESB (Enterprise Service Bus) with 23 reviews while webMethods Integration Server is ranked 3rd in ESB (Enterprise Service Bus) with 60 reviews. Red Hat Fuse is rated 8.2, while webMethods Integration Server is rated 8.0. The top reviewer of Red Hat Fuse writes "Configurable, doesn't require much coding, and has an automatic load balancing feature, but its development features need improvement". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". Red Hat Fuse is most compared with Mule ESB, IBM Integration Bus, Oracle Service Bus, WSO2 Enterprise Integrator and JBoss ESB, whereas webMethods Integration Server is most compared with webMethods.io Integration, IBM Integration Bus, Mule ESB, TIBCO BusinessWorks and Oracle Service Bus. See our Red Hat Fuse vs. webMethods Integration Server report.
See our list of best ESB (Enterprise Service Bus) vendors.
We monitor all ESB (Enterprise Service Bus) 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.
With webMethods Integration Server, you have the power to connect anything faster, thanks to open, standards-based integration. Make custom, packaged and mainframe applications and databases—on-premises and in the cloud—interoperable and assure the fluid flow of data across your automated processes. Mapping and transformation functions are built-in.
pro's; Easy scalability, 300+ connectors, Faster integrations, "Lift & shift" integrations, Mapping and transformation & iPaaS integrations in the cloud
Where Red Hat Fuse, pros; Hybrid deployment, Built-in iPaaS with low-code UI/UX, Container-based integration & Integration everywhere supporting 200 included connectors.
Red Hat Fuse, based on open source communities like Apache Camel and Apache ActiveMQ, is part of an agile integration solution. Its distributed approach allows teams to deploy integrated services where required. The API-centric, container-based architecture decouples services so they can be created, extended, and deployed independently.
Hello Andhika
Please read Dave's reply first and understand that WebMethods offers many features that you will not find in RedHat Fuse.
I would like to add one more architectural point of view.
WebMethods provides a nice business process engine that helps you orchestrate your services. Fuse is not able to provide this kind of service.
If your processes are simple and map information, for example, use Fuse.
If your business processes are complex and require balancing, I recommend an integration tool with a business process engine (BPEL or BPMN). WebMethods, Oracle SOA Suite or OpenESB offer these types of tools.
If you plan to design complex processes, you should not hesitate to choose WebMethods.