APIC, a decent pick that could do better
July 03, 2023

APIC, a decent pick that could do better

Roberto De Gasperi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with IBM API Connect

API Connect acts as an exposure layer (ingress point), fronting our integration bus services components. Providing a TLS termination point, authentication, fine grained authorisation, and rate limiting capabilities.
  • Open API Specification authoring
  • API and API Product lifecycling
  • Self service
  • Adherence to industry standards e.g. W3C SOAP specifications
  • Validation policy breadth and depth
  • Full OAS support
  • More secure APIs
  • Higher consistency of interface specifications
Look and feel has changed over the years, this can make it difficult to keep up
It really simplifies the job of downstream components and promotes clear separation of concerns between functions and development team
  • Kong Gateway Community (Open Source)
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

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

Yes

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

Yes

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

No

Did implementation of IBM API Connect go as expected?

Yes

Would you buy IBM API Connect again?

Yes

Well suited scenarios: Use as an API gateway, ingress point for ReSTful HTTP(S) interfaces / services. Less appropriate: Use as an API gateway, ingress point for SOAP interfaces / services

IBM API Connect Feature Ratings

API access control
10
Rate limits and usage policies
10
API usage data
10
API user onboarding
10
API versioning
10
Usage billing and payments
Not Rated
API monitoring and logging
10