ICT Architect at a tech services company with 51-200 employees
02 May 22
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:
- Concept of catalogs is useful (for us) w.r.t. dealing with several tenants.
- When it is running, it looks very stable.
- 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.
I have worked on 5 API products each product has its own pros & cons. I would choose Apigee over all others because it provides pure API Management Tools & Services. Apigee also provides a lot of OOTB Policies which can be applied with little or no change. API Development & Exception handling is too easy in Apigee compared to Mulesoft.
Go for Mulesoft if ESB capabilities are required and unlike APigee we can do a lot of customization & create custom policies in Mulesoft. Mule also provides a lot of third-party connectors OOTB which can be used to quickly integrate with other systems. We can also create custom connecters as per our requirement.
Apigee supports Swagger & Mule supports RAML. So if your existing services/APIs produce/use Swagger go for Apigee. Anyway, we have many scripts which convert Swagger to RAML & vice-versa.
A very good Developer/API Portal is required for exposing the APIs securely & well-documented. If this is an important requirement, I would recommend Apigee over Mulesoft. Apigee's Drupal-based Portal provides a lot of features which Mulesoft Portal lacks.
Apigee also provides features/tools on Analytics & Bot-Detection for improving your APIs consumption.
Enterprise Architect & Principal Consultant at a tech services company with 10,001+ employees
22 March 18
It depends on your needs. I would recommend Apigee if you are don’t need an Integration Platform/ ESB for any heavy lifting. Mulesoft Cloudhub comes with one common engine “Mule Anypoint Runtime Engine” which is the core and offers ESB capabilities including a lot of OOTB connectors.
Now if your southbound/ downstream has a lot of legacy applications requiring message/ file based integrations, then it makes sense to use Mulesoft, wrap these legacy-interfaces as HTTP/Web end-points and wire them using API Manager.
On the other hand, if you downstream is already on HTTP endpoint/ microservices, then Apigee is far more robust than API Manager. You can simply scale it to 200tps without any hassle. The deployment model of Apigee is lot cleaner as you can scale the “Message Processor & Message Router” (part of Edge gateway) separately from Dev Portal & Management server. The analytics is far superior to Mule and you far more options when wiring API than Mule. For example, the concept of IP-whitelisting, data policies (as filters) is pretty cool in Apigee. Another key point is you can have a hybrid model in Apigee with on-prem Message Router(s) to deploy multiple clusters of microservices. I have not used BaaS but it gives you the ability to create “Application Network” very similar to Mule except it looks richer.
Finally, with zookeeper, clustering of Apigee Edge server is more robust than Mulesoft, especially on higher loads. My verdict is Apigee if Integration is NOT a need.
BTW, I felt API Manager’s Anypoint Exchange is a better collaboration platform for sharing API definition within enterprise and outside. It's actually nice ?. But with Salesforce acquisition of Mulesoft, please understand their long-term roadmap and support/upgrade (especially if you going with On-Premise and not on cloud).