IBM API Connect is a scalable API solution that helps organizations implement a robust API strategy by creating, exposing, managing and monetizing an entire API ecosystem across multiple clouds. As businesses embrace their digital transformation journey, APIs become critical to unlock the value of business data and assets. With increasing adoption of APIs, consistency and governance are needed across the enterprise. API Connect aims to help businesses…
N/A
IBM webMethods
Score 8.7 out of 10
N/A
IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
N/A
Pricing
IBM API Connect
IBM webMethods
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM API Connect
IBM webMethods
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM API Connect
IBM webMethods
Considered Both Products
IBM API Connect
Verified User
Anonymous
Chose IBM API Connect
Ease of use of the product and pricing of the product.
Prior to adopting IBM API Connect, there were two main competitors, MuleSoft. Although in the integration capabilities MuleSoft seemed to have an advantage, and regarding developer experience, IBM API Connect had a set of enterprise features for the API management.
Mulesoft seemed to take a lot longer to implement and reach any real ROI attribution. For the other competitors, I'd say they are easier to administrate, but this isn't as important to us as a business user. It was easier to explore APIs with IBM than it was with others.
There were multiple product we read and then shortlist were taken as POC against IBM API Connect. -Google Apigee : is good but in cross cloud there are concerns. Also, feature of reading & identifying the target system certificate was not available there.
It was organizational boundaries to use IBM API Connect but we have learnt so many think on this technology. Obviously, We have more experience on this it;s easy for us to configure and maintain the system.
IBM API Connect have more feature compared to other solutions like from one platform we can create APIs on the API Manager, we can publish the APIs to the products/portal server, we can secure the APIs using IBM DataPower Gateway, we can socalize the APIs using developer …
We use IBM Cloud, which works well with our hybrid cloud deployment. As a large firm, we are able to scale as required once the initial setup is complete.
There are two main reasons for choosing IBM over others. 1) Pricing 2) The conversation during the sales stage. The team at IBM understood our requirements and acted as consultants instead of sales people. They genuinely focused on providing a solution to our pain points which …
IBM APIC far and away blows the other two systems I've used out of the water. There really isn't any comparison, in my humble opinion. Ease of use, security, versioning, efficiency, accountability are basically 'forced' by APIC, which allows less burden on the users themselves.
IBM API Connect and Apigee are both robust API management platforms. IBM API Connect was selected for its strong integration capabilities, hybrid cloud deployment options, and comprehensive analytics. It aligns well with organizations seeking flexibility and control over their …
API Connect was far more mature, far quicker than Kong. It was clear a few years ago that API Connect features such as Applications and Product groupings were the way forward as Kong was at the time lacking these but planning to replicate them in their roadmaps
This is more of a combinatory set of features where it isn't a question of either or, but rather what and how when. Choosing the right tool and implementation format for the problem at hand - and having the option to select tooling from the full set in the toolbox.
IBM webMethods lags in terms of iPass offering as compared to mulesoft and dell Boomi. In terms of api management Apigee is much better than webMethods.
IBM webMethods is far superior when compared to competition like Microsoft Azure. In functionality and capabilities. Better visibility, uptime, efficiency, etc.
webMethods does better for end to end integrations whereas Azure is more focused on APIs. We selected webMethods because we felt their integrations, especially to mainframe environments, were much better than the others. IBM has been in this space for a long time and know it …
Oracle Integration Cloud vs IBM webMethods, hands down IBM webMethods is way better. Lots of features and ease of doing webMethods and super stable stack.
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 …
IBM webMethods was selected vs WSo2 for the reachness of the correspondign features regarding Mulesoft, the flexibility of IBM webMethods compared to the other platform, in relation to the existing architectural landscape was preferred
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. …
I have seen that other products have different UI to address various business problems like messaging, EDA, MFT. IBM webMethods has unified platform and can also support hybrid Integration. I think it is all rounded iPaaS tool with ease of development and ease of operation. The …
The webMethods platform ranks higher in our ranking because it has more features and has proven itself in many CAC 40 companies in particular.The key elements are robustness, ease of use, a clear business model, and a wide range of features covering all types of enterprise …
IBM webMethods combines all the essential functions for information system integration in its platform. All products are interconnected to facilitate implementation (ESB, API, BPM, message bus). All tools are easy to use.
Overall, it can be stated that IBM API Connect has many benefits and can easily manage complicated integrations. The platform performs best in large environments, especially where microservices and processing of multiple API dependencies are required. On average, we have processed thousands of API calls within a second with good response time.
With its world-class proven technology, the IBM webMethods products are best suited for solving integration needs, including application connectivity, data aggregation, and data synchronization. The business use cases expand across Healthcare, Aviation, Banking, Insurance, etc., and many other mission-critical systems. Though I feel there is room for improvement where webMethods products are utilized in a containerized platform, especially with the API Management suite of products.
That being stated, every thing you own will have both positive and negative aspects to its use. It can be perplexing at times, particularly when navigating between different functions.
However, based on my usage of this application up until this point, I've discovered that the only time it lags is when it's downloading updates. Otherwise, it's excellent to utilise for all other customs.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
IBM API Connect may be less appropriate for small-scale projects with minimal API management requirements, where simpler and more cost-effective solutions suffice. Organizations lacking the necessary technical expertise or resources to harness its full potential may face implementation challenges. In static environments with infrequent API changes or limited developer engagement, the platform's comprehensive features may be excessive for the task at hand.
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
We received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
Our decision to adopt IBM API Connect was driven by its comprehensive end-to-end API lifecycle management, which proved to be exceptionally well-suited to our B2B, Open Banking, and multi-fintech integration requirements. When compared with other solutions, API Connect stood out for its ability to externalize and govern APIs at scale, while offering enterprise-grade capabilities critical for our regulated environment. IBM App Connect serves as our internal integration middleware, focused on backend orchestration and data transformation. IBM watsonx acts as a complementary AI and data platform for exposing intelligent services especially with the code assistant functionality, it is API Connect that provides the crucial layer for external API exposure, management, and monetization. IBM DataPower is an incredibly secure and performant runtime, and lacks key enterprise features such as developer engagement, full API governance, and analytics. API Connect fills that gap seamlessly, offering a unified, secure, and scalable API management experience.
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. Pricing and licensing model, cloud strategy, and level of distributed responsibilities and ownership of integration in the organisation can be deciding factors.
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
