Apigee Edge is an API management platform now owned and offered by Google, since Google acquired Apigee in 2016.
N/A
IBM App Connect
Score 9.4 out of 10
N/A
IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
IBM API Connect is positioned ahead of Apigee in the Gartner report. But in my opinion the development experience and the data transformation capability is way better in Apigee and it’s a proved solution and has a huge client list. (I have worked on an American Express …
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
- 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
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.
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.
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.
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.
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.
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
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.
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.
