IBM API Connect vs. IBM App Connect

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.

Incentivized

- 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

• API discovery feature is very helpful to allow us to scope the work required before diving into things.
• The ability to set permissions and rulesets at a user level is essential to restrict access to specific datasets.
• Ability for external users (those from outside our organisation) to leverage the API in more restrictive manner.

Incentivized

• 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.

Incentivized

• Improvement can come in the interface of the tool, which is sometimes complex and requires a deep understanding of the tool.
• Improving the different levels of access to the playroom could be helpful because product owners and developers need to see other information.
• Publishing API and integration of API can be more straightforward.

Incentivized

• 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.

Incentivized

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.

Incentivized

I have given an 8 out of 10 rating because I believe multiple authentication security techniques, such as OAUTH, MTLS, JWK, etc., are supported out of the box for APIs. A single interface may be used for API development, automation, and administration, ensuring security and boosting productivity. Highly regarded compared to its rivals, indicating that it has provided good service over time. Although It takes a lot of time and effort to set up initially. However, once everything is set up, it is quite simple to administer, especially because there is only one interface to utilize. This makes it very straightforward to handle.

Incentivized

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.

Incentivized

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.

Incentivized

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 ecosystems, especially when dealing with complex integration scenarios across diverse environments.

Incentivized

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.

Incentivized

• Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used.
• Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients.
• Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.

• I don't see any negative Impact .
• I like using this tool to do my job.
• I am comfortable using this tool.

Incentivized