Apigee Edge vs. IBM App Connect

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

Incentivized

IBM App Connect Enterprise is well-suited for high-volume enterprise systems that demand robust scalability and high reliability. It excels at hybrid connectivity by easily integrating various on-premises systems using its extensive catalog of connectors. It is also ideal for workflows that require a balance between efficient low-code and the incorporation of complex, custom Java logic. On the other hand, the platform is less appropriate in scenarios requiring high development autonomy, as installation and configuration at the server level is excessively complex, creating a strong dependency on other infrastructure teams. It is also not ideal if detailed traceability and monitoring of workflows must be seamlessly managed within the tool itself, as this is difficult to manage directly in ACE. IBM App Connect Enterprise está bien adaptado para sistemas empresariales de alto volumen que exigen una escalabilidad robusta y alta confiabilidad. Sobresale en la conectividad híbrida al integrar fácilmente diversos sistemas locales (on-premises) utilizando su amplio catálogo de conectores. Además, es ideal para flujos que requieren un equilibrio entre el low-code eficiente y la incorporación de lógica Java compleja y personalizada. Por otro lado, la plataforma es menos apropiada en escenarios donde se requiere una alta autonomía de desarrollo, debido a que la instalación y configuración a nivel de servidor es excesivamente compleja , lo cual crea una fuerte dependencia de otros equipos de infraestructura. Tampoco es ideal si la trazabilidad detallada y el monitoreo de los flujos deben gestionarse sin problemas dentro de la propia herramienta, ya que esto resulta difícil de manejar directamente en ACE. Parts of this review were originally written in Spanish and have been translated into English using a third-party translation tool. While we strive for accuracy, some nuances or meanings may not be perfectly captured.

Incentivized

• Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions.
• Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy.
• Very good documentation and blog with details of most common failures and error handling.
• A very very easy to use console.

Incentivized

• Just the ability to display and consume data through a single dashboard makes this a great application for our business purposes.
• With the ability to consume their exposed API, data validation and manipulation becomes a breeze.

Incentivized

• Only one user can be active in a proxy at a time
• No version control
• 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.

Incentivized

• modernization made easy, when a modernized project is created by importing a java code.
• more pre-built connectors
• watsonx code assistance for ESQL capability.

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.

Incentivized

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.

Incentivized

Support has helped us to resolved all the queries and community support was also good.

Incentivized

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.

Incentivized

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.

Incentivized

Usually, the IBM Ops team provides a resolution or a response for 80% of defects raised in my project. There is one which has been open on their end for more than 3 months. With literally no response even after multiple follow-ups.

Incentivized

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

Incentivized

IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in the latest version are preparing it for a Cloud/containers world without losing the previously learned knowledge.

• 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.

Incentivized

• We never implemented Cast Iron in production. When compared to five competing products in the iPaaS space it didn't make it past the first few test scenarios we threw at it.

Incentivized