Azure API Management vs. IBM Cloud Pak for Integration

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure API Management
Score 8.1 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
IBM Cloud Pak for Integration
Score 8.4 out of 10
N/A
IBM Cloud Pak for Integration is deisgned to drive digital transformation with a simple, complete solution to support a modern approach to integration, enabling teams to integrate three times faster, while reducing cost by one-third.N/A
Pricing
Azure API ManagementIBM Cloud Pak for Integration
Editions & Modules
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
No answers on this topic
Offerings
Pricing Offerings
Azure API ManagementIBM Cloud Pak for Integration
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Features
Azure API ManagementIBM Cloud Pak for Integration
API Management
Comparison of API Management features of Product A and Product B
Azure API Management
8.0
4 Ratings
2% below category average
IBM Cloud Pak for Integration
-
Ratings
API access control8.94 Ratings00 Ratings
Rate limits and usage policies5.44 Ratings00 Ratings
API usage data8.94 Ratings00 Ratings
API user onboarding9.03 Ratings00 Ratings
API versioning8.94 Ratings00 Ratings
Usage billing and payments5.23 Ratings00 Ratings
API monitoring and logging9.84 Ratings00 Ratings
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Azure API Management
-
Ratings
IBM Cloud Pak for Integration
8.3
1 Ratings
2% above category average
Pre-built connectors00 Ratings8.01 Ratings
Connector modification00 Ratings7.01 Ratings
Support for real-time and batch integration00 Ratings9.01 Ratings
Data quality services00 Ratings7.01 Ratings
Data security features00 Ratings9.01 Ratings
Monitoring console00 Ratings10.01 Ratings
Best Alternatives
Azure API ManagementIBM Cloud Pak for Integration
Small Businesses
NGINX
NGINX
Score 9.0 out of 10
Make
Make
Score 9.2 out of 10
Medium-sized Companies
NGINX
NGINX
Score 9.0 out of 10
Zapier
Zapier
Score 8.9 out of 10
Enterprises
NGINX
NGINX
Score 9.0 out of 10
SAP Integration Suite
SAP Integration Suite
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure API ManagementIBM Cloud Pak for Integration
Likelihood to Recommend
8.0
(4 ratings)
7.0
(1 ratings)
User Testimonials
Azure API ManagementIBM Cloud Pak for Integration
Likelihood to Recommend
Microsoft
APIM is useful for the standard scenarios:
1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.
2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.
3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.
Read full review
IBM
We are always working on improving our brand - good customer care and efficient services are the roads to that. By picking IBM's AI automation, we are able to coordinate and connect processes around the company to deliver efficient services on store and online on our website. We've been able to seamlessly automate and digitize most of our operations.
Read full review
Pros
Microsoft
  • Easy commissioning of APIs.
  • Great policies to control access.
  • Easy mock services for testing.
Read full review
IBM
  • Test generation gives useful insights into missing tests before launching the bots.
  • Open API files helps us understand what is running behind the scenes.
Read full review
Cons
Microsoft
  • Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
  • As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
  • Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.
Read full review
IBM
  • Natural language processing needs more attention to have more flowing conversations.
Read full review
Alternatives Considered
Microsoft
Azure APIM vs Amazon API Gateway:
1) Azure APIM was a complete package that included a developer portal.
2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.
Read full review
IBM
No answers on this topic
Return on Investment
Microsoft
  • We can always think of positive ROI impact on business
  • It helps to easily facilitate the design, deployment, and maintenance of our APIs
Read full review
IBM
  • Achieving consistency across operations.
  • IBM RPA provides bots to handle the micron tasks which are monotonous and boring.
Read full review
ScreenShots