No more typing reviews! Try our Samantha, our new voice AI agent.

Confluent vs IBM webMethods Hybrid Integration comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Confluent
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (7th)
IBM webMethods Hybrid Integ...
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
95
Ranking in other categories
Business-to-Business Middleware (5th), Enterprise Service Bus (ESB) (4th), Managed File Transfer (MFT) (13th), API Management (16th), Cloud Data Integration (12th), Integration Platform as a Service (iPaaS) (12th)
 

Featured Reviews

PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.
YM
Developer at a hospitality company with 1,001-5,000 employees
Offers strong integration capabilities and reliable features but needs pricing and scaling improvements
Many things are evolving with the AI buzz in the market. What I would like to see improved or enhanced in webMethods.io in the future is that since webMethods.io is already under IBM, I think IBM will introduce and integrate AI into it. Additionally, regarding what webMethods.io can improve is the license cost. Other cloud players are also providing the same kind of functionality, such as AWS and Azure. webMethods.io is being installed on-premises, but AWS is providing it directly in the cloud. When comparing the license cost and request per minute cost, webMethods.io needs to address that. There are many competitors in the market for this.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"The design of the product is extremely well built and it is highly configurable."
"The solution can handle a high volume of data because it works and scales well."
"Their tech support is amazing; they are very good, both on and off-site."
"Confluent is an amazing tool that is highly configurable, integrates very well with Jira, and lets you create nice documentation for various products while also supporting reporting and online content hosting."
"We mostly use the solution's message queues and event-driven architecture."
"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"Currently, we're using this solution for the integration server which helps us to integrate with the mainframe."
"The solution is scalable."
"It gives value for your money, and it is easy to implement and maintain."
"I like the tool's scalability."
"It has a good integration server, designer, and a very good API portal."
"It is a very stable product."
"The most valuable feature is stability."
"Overall, webMethods offers a good user experience and is easy to use for our company."
 

Cons

"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"From the control center perspective, there is a lot of room for improvement in the visualization."
"Confluent has a good monitoring tool, but it's not customizable."
"Confluent's price needs improvement."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"It would be great if the knowledge based documents in the support portal could be available for public use as well."
"One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it challenging to manage access at scale if we have many different data sources."
"The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include."
"A potential drawback of webMethods.io API is its adaptability to legacy systems, which can vary in compatibility."
"The solution has big instances when deployed under microservices or in a containerized platform. They need to improve that so that it is competitive with other integration solutions, like Redis and Kafka. Deployments under microservices with those solutions are much more lightweight, in the size of the runtime itself, compared with Software AG."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
"The products, at the moment, are new and there should perhaps be support for the older version of the protocols."
"The installation process is very complex, there being many products, each having its own."
"There are things that could be improved with the webMethods API gateway. One thing is that it's too attached to the integration service and we'd like it to be a little bit more independent. We would like for them to separate operations so that it doesn't rely on the bulky integration server and so that it can be used everywhere."
"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."
"This product is for larger companies. Compared to TIBCO I think webMethods is better in terms of ease of use and support."
 

Pricing and Cost Advice

"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"It comes with a high cost."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"Confluent is highly priced."
"The solution is cheaper than other products."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"I don’t have much idea about prices, but webMethods API Portal is not something cheaper."
"The pricing is a yearly license."
"webMethods.io is expensive. We have multiple components, and you need to pay for each of them."
"It is an expensive tool. I rate the product price a nine out of ten, where ten means it is very expensive."
"Pricing has to be negotiated with the local Software AG representative. SAG can always prepare an appropriate pricing model for every client."
"With our current licensing, it's very easy for us to scale. With our older licensing model, it was very hard. This is definitely something that I would highlight."
"The price is a little bit high, especially regarding their support."
"webMethods Trading Networks is a bit costly compared to others solutions."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,153 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
12%
Computer Software Company
8%
Manufacturing Company
6%
Manufacturing Company
12%
Financial Services Firm
10%
Construction Company
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business23
Midsize Enterprise11
Large Enterprise65
 

Questions from the Community

What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
What needs improvement with webMethods Integration Server?
The alignment of on-premise and cloud versions needs improvement.
What needs improvement with webMethods Trading Networks?
webMethods.io does not currently have certain features, and we have to do coding as well. However, they have recently come up with a hybrid application where users will be able to use drag-and-drop...
What is your primary use case for webMethods Trading Networks?
We are primarily focused on IBM webMethods. I am part of the Center of Excellence team, where we involve ourselves in proposals and providing solutions to clients. webMethods.io is a middleware too...
 

Also Known As

No data available
Built.io Flow, webMethods Integration Server, webMethods Trading Networks, webMethods ActiveTransfer, webMethods.io API
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Cisco, Agralogics, Dreamforce, Cables & Sensors, Sacramento Kings
Find out what your peers are saying about Confluent vs. IBM webMethods Hybrid Integration and other solutions. Updated: August 2026.
909,153 professionals have used our research since 2012.