We are currently evaluating the integration platform that we want to use to manage (API Gateway / policy management) and build our integrations. Our goal is to reduce time-to-market for APIs, and better manage our API landscape (without letting the platform costs spin out of control). Down to the final two now -- MuleSoft and Azure (we have historically been a Microsoft shop), and the results are too close to call. For those who have gone through a similar evaluation, how did you make your final decision?
Sort By:
Oldest
Technology Leader in Healthcare and Biotech2 months ago
It depends on where you entire infrastructure ecosystem is deployed, these days most public cloud provider have their native API management example Google Apigee X etc. Vice President in Bankinga month ago
I completely agree with this. It really depends on your infrastructure.
CIO in Healthcare and Biotech2 months ago
It depends on your needs but I have used both Boomi and most recently Workato. Workato is easier to manage and build connections than Boomi but both are solid products in my experience. Director of Information Security2 months ago
What are you using to build your integration, full Mule stack or Azure Integration Services? That should drive your decision. If AIS then I would go Azure APIM given the level of integrations or Mule if you are buying into the full Mule vision including leveraging their methodology. We use both, but Mule is restricted to use as an integration to Salesforce given the level of integration and AIS for all other integrations. Director of IT in Services (non-Government)2 months ago
We had a similar situation when we first started leveraging APIs and conducted multiple gateway evaluations over the years. Currently, as our AWS footprint has increased significantly, we are leveraging AWS' API Gateway. Mulesoft was one of the top vendors we looked at. As was APIGee. Both have robust offerings and rich feature sets - more so than AWS' gateway eg developer experience/portal - but the decision was to go with AWS and fill the gaps with other approaches. CIO2 months ago
It's a close call, but for me, it would depend on whether we're prioritizing a broad range of features and complex integrations (MuleSoft) or a tighter integration with our existing Azure infrastructure (Azure API Management). If cost is a major factor, Azure might be the way to go, but we'd need to weigh that against the potential need for additional tools or services to achieve the same functionality as MuleSoft.