Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
IBM Cloud Pak for Integration
Score 7.5 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 Management
IBM 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 Management
IBM Cloud Pak for Integration
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure API Management
IBM Cloud Pak for Integration
Features
Azure API Management
IBM Cloud Pak for Integration
API Management
Comparison of API Management features of Product A and Product B
Azure API Management
8.0
4 Ratings
5% below category average
IBM Cloud Pak for Integration
-
Ratings
API access control
8.94 Ratings
00 Ratings
Rate limits and usage policies
5.44 Ratings
00 Ratings
API usage data
8.94 Ratings
00 Ratings
API user onboarding
9.03 Ratings
00 Ratings
API versioning
8.94 Ratings
00 Ratings
Usage billing and payments
5.23 Ratings
00 Ratings
API monitoring and logging
9.84 Ratings
00 Ratings
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
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.
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.
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.