IBM App Connect vs. webMethods.io Integration

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
IBM App Connect
Score 8.6 out of 10
N/A
IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.N/A
webMethods.io Integration
Score 8.9 out of 10
N/A
webMethods.io Integration (formerly webMethods Integration Cloud) from Software AG is designed to make it easy to connect SaaS apps and make business processes more efficient. It enables enterprise subject matter experts and eliminates integration silos, allowing users to integrate applications hosted in public or private clouds, as well as applications hosted on premises.N/A
Pricing
IBM App ConnectwebMethods.io Integration
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM App ConnectwebMethods.io Integration
Free Trial
YesNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
IBM App ConnectwebMethods.io Integration
Top Pros
Top Cons
Features
IBM App ConnectwebMethods.io Integration
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
IBM App Connect
8.8
7 Ratings
7% above category average
webMethods.io Integration
7.7
1 Ratings
6% below category average
Pre-built connectors9.07 Ratings8.01 Ratings
Connector modification8.16 Ratings9.01 Ratings
Support for real-time and batch integration9.07 Ratings8.01 Ratings
Data quality services9.07 Ratings7.01 Ratings
Data security features9.07 Ratings7.01 Ratings
Monitoring console8.87 Ratings7.01 Ratings
Best Alternatives
IBM App ConnectwebMethods.io Integration
Small Businesses
Make
Make
Score 9.2 out of 10
Make
Make
Score 9.2 out of 10
Medium-sized Companies
Zapier
Zapier
Score 8.9 out of 10
Zapier
Zapier
Score 8.9 out of 10
Enterprises
SAP Integration Suite
SAP Integration Suite
Score 8.7 out of 10
SAP Integration Suite
SAP Integration Suite
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
IBM App ConnectwebMethods.io Integration
Likelihood to Recommend
9.0
(8 ratings)
9.0
(1 ratings)
Likelihood to Renew
9.0
(1 ratings)
-
(0 ratings)
Usability
8.0
(1 ratings)
-
(0 ratings)
Support Rating
8.0
(2 ratings)
-
(0 ratings)
User Testimonials
IBM App ConnectwebMethods.io Integration
Likelihood to Recommend
IBM
- great when you need to integrate applications without any message lost or duplicated and when transnationality is important - if you need the highest throughput possible and not much (or not at all) mapping is required, a system like Kafka is more appropriate
Read full review
Software AG
We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.
Read full review
Pros
IBM
  • Just the ability to display and consume data through a single dashboard makes this a great application for our business purposes.
  • With the ability to consume their exposed API, data validation and manipulation becomes a breeze.
Read full review
Software AG
  • Easy to use
  • Priced competitively
  • Supports robust and resilient integration solutions
Read full review
Cons
IBM
  • The development and the transformation capability is not so great. I believe IBM is looking to incorporate some of features of IBM APP Connect into API Connect.
  • The authentications features are no way close to CA API Management (f.k.a Laye r7).
  • The development experience is not as good as Apigee's.
  • The GUI should be improved. Maybe the product team should see the other API management tools in their offering.
Read full review
Software AG
  • Complex logic is hard to understand in simple diagrammatic user interface
  • User interface too simplistic for solutions that are complicated or go against the grain
  • Runtime observability could be improved
Read full review
Likelihood to Renew
IBM
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
Read full review
Software AG
No answers on this topic
Usability
IBM
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
Read full review
Software AG
No answers on this topic
Support Rating
IBM
Support is good, however it takes longer than expected to get responses. When bugs are reported they often seem to fall into a black hole.
Read full review
Software AG
No answers on this topic
Alternatives Considered
IBM
We did not select Cast Iron as our iPaaS solution, it was the weakest competitor in the field that we evaluated. Our experience was that it was not nearly as easy to learn, without in-depth training and guidance, and the developer UI was extremely buggy. We subjected each of the vendors to a battery of integrations, from simple to challenging, and it fell short on each one. One of the most simple integrations was grabbing a CSV file from an FTP source, parsing the data, doing a small amount of transformation, then inserting that data into an Azure MSSQL DB. After 2 hours on the phone with the Cast Iron support team, we were still unable to get this working.
Read full review
Software AG
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
Read full review
Return on Investment
IBM
  • I don't see any negative Impact .
  • I like using this tool to do my job.
  • I am comfortable using this tool.
Read full review
Software AG
  • webMethods.io Integration is a cost effective approach to integration in isolation
  • webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs
  • webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps
  • webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used
Read full review
ScreenShots