Apigee Edge is an API management platform now owned and offered by Google, since Google acquired Apigee in 2016.
N/A
IBM API Connect
Score 8.8 out of 10
N/A
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…
The power of IBM APIC is much more in contrast to Apigee or any other product of the same domain because it is having DataPower as the backbone which allows for easy integrating with almost any platform, providing the highest level of security, handling millions of transactions …
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 …
We choice IBM API Connect because Apigee is more manual when you create an API Proxy
Verified User
Program Manager
Chose IBM API Connect
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.
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.
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 …
Vice President & Head Technology COE -Open Banking, FinTech, CRM, Wealth Management, HR & Finance
Chose IBM API Connect
We selected API connect as both tools have more or less same features, the differentiation was we also use IIB, and seamless integration with IIB was the major factor
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
Based on our experience, IBM API Connect clearly excels in large enterprises navigating complex B2B ecosystems, especially within the Fintech and Banking sectors. Its capabilities are particularly valuable for achieving Open Banking compliance, facilitating the monetization of data and services, and seamlessly operating in hybrid cloud environments. However, it's crucial to understand that IBM API Connect primarily functions as an API management and orchestration tool. This means that backend integrations with providers like databases are best handled by dedicated integration middleware, such as IBM App Connect, allowing API Connect to then securely and efficiently expose those functionalities to external entities.
Prohibited from using JSON.stringify on Apigee objects (tokens)
Debugging is difficult
Unable to rename or delete policies without bumping revision
Why would anyone give a js policy one name, display name something else, and script a different name?
'Trace' limited to only 20 transactions
UI allows users to add target servers, but users must utilize the api to turn on SSL.
I'm sure there's more, they just aren't coming to mind right now.
Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
I can honestly say that the availability of the platform has been incredible, with almost no disruptions during the two years of the implementation. Availability is provided through the distributed architecture that may be deployed in multiple zones. We have had almost no cases of unplanned outages, and most maintenance operations were done during planned downtimes.
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
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.
As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.
Our company benefited from IBM API Connect's assistance in establishing cooperation with our outside providers and efficiently managing the API. As a result, we were able to expand our vendor ecosystem.
Additionally, creating APIs and implementing them on the goods was not too difficult. Additionally, we were able to ensure that only appropriate people could publish the APIs following evaluation by using role-based access control.
Our teams were able to reuse and share departmental APIs and services with each other thanks to the simple, self-service developer site.