We are using API Connect for approx. 10 months. It has been (and still is) a very stony road. We are now considering another solution.
My findings w.r.t to API Connect:
Pros:
- Concept of catalogs is useful (for us) w.r.t. dealing with several tenants.
- When it is running, it looks very stable.
Cons:
- Installation and updates were a nightmare each time. We use OpenShift; and we had problems for up to three weeks for an update, including support from IBM. We cannot afford that in production, which leads to investigations on our side.
- Small amount of policies, compared to some of the competitors. In the current version, a "map" is not supported (according to IBM).
- No debugging of the flow.
- High footprint of pods and resources, compared to an alternative.
Hello peers,
I am a Business Analyst at a large consultancy firm.
I am currently researching API Management Platforms.
Which product do you prefer: Apigee, MuleSoft Anypoint API Manager, or IBM API Connect? Which product has the best service offerings and which is the most cost-friendly?
Thank you for your help.
Hello peers,
I am the Head of IT, Strategy, and Finance at a large bank.
I am currently researching API management tools.
Which solution do you prefer: Apigee or API Connect? What are the pros and cons of each solution?
Thank you for your help.
Data Office Lead at a comms service provider with 501-1,000 employees
Nov 24, 2022
Both Google Apigee and IBM API Connect offer versatile and robust API management capabilities. If managing APIs for a SaaS stack and integrating with 3rd party applications is your primary objective Apigee might prove to be a better fit, while if you are looking at enabling digital capabilities for a complex set of applications, mainframes, and other traditional components is your motive, then API Connect might have a few tricks up its sleeve.
I suggest you look at the bigger picture. Do you have other integration requirements besides APIs? What about legacy systems, events, and file transfers? Are you looking for a distributed API solution or a cloud-based? What is your infrastructure/runtime strategy (bare metal/containers)?
If this is the case, you should take a look at Cloud Pack for Integration. It has different things I like. First, it has a bunch of capabilities (queue management, API gateway, and management, Kafka, high-speed file transfer, etc). Second, it runs in containers (specifically Red Hat OpenShift), so you can run it in different cloud providers or locally.
PeerSpot’s crowdsourced user review platform helps technology decision-makers around the world to better connect with peers and other independent experts who provide advice without vendor bias.
Our users have ranked these solutions according to their valuable features, and discuss which features they like most and why.
You can read user reviews for the Top 5 Integration Platform as a Service ...
We are using API Connect for approx. 10 months. It has been (and still is) a very stony road. We are now considering another solution.
My findings w.r.t to API Connect:
Pros:
- Concept of catalogs is useful (for us) w.r.t. dealing with several tenants.
- When it is running, it looks very stable.
Cons:
- Installation and updates were a nightmare each time. We use OpenShift; and we had problems for up to three weeks for an update, including support from IBM. We cannot afford that in production, which leads to investigations on our side.
- Small amount of policies, compared to some of the competitors. In the current version, a "map" is not supported (according to IBM).
- No debugging of the flow.
- High footprint of pods and resources, compared to an alternative.
Hi @Pradeep Pavuluri, @Bert Van Vugt , @Balakrishnan Vinchu, @Carlos Maximo Ramos, @Clement Hsieh, @Augustine Ayo and @Irshad Ahamed,
Can you please chime in and assist @Pepe Redondo Rubio?