Item: IBM API Connect
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We implemented API Connect as a central API Management layer.

Pros and Cons

Flexible API Gateway
Organisation of APIs into a API Portfolio
Subscription and Lifecycle Management

Stability of niche use cases on the API Gateway
API Portal needs a multi catalogue option
Hooks to alter the workflows in API Manager - Axway is much more customizable here

From my experience, you need a high skill level to operate the management platform itself. Also, I feel that developers have too much freedom and there is no clear way to inform things like minimum security requirements.

API Security

In my opinion, it's easier to enforce OAuth Token introspect. In many parts there are missing features where we needed to develop functionality our self to fulfill the features we needed in an enterprise context.

Alternatives Considered

Axway AMPLIFY API Management, Apigee Edge and Kong Gateway Community (Open Source)

Key Insights

Do you think IBM API Connect delivers good value for the price?

Yes

Are you happy with IBM API Connect's feature set?

Did IBM API Connect live up to sales and marketing promises?

Yes

Did implementation of IBM API Connect go as expected?

Would you buy IBM API Connect again?

Yes

Other Software Used

Axway AMPLIFY API Management

Likelihood to Recommend

Stand alone API Management - well suited

General Integration Platform - Mulesoft much stronger

IBM API Connect

Overall Satisfaction with IBM API Connect