Try our new research platform with insights from 80,000+ expert users

IBM Cloud Pak for Integration vs Microsoft Azure API Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Cloud Pak for Integration
Ranking in API Management
24th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
Cloud Data Integration (16th)
Microsoft Azure API Management
Ranking in API Management
1st
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
81
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the API Management category, the mindshare of IBM Cloud Pak for Integration is 0.5%, down from 0.6% compared to the previous year. The mindshare of Microsoft Azure API Management is 17.9%, down from 19.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

Neelima Golla - PeerSpot reviewer
A hybrid integration platform that applies the functionality of closed-loop AI automation
I recommend using it because, in today's context, the cloud plays a significant role. Within the same user interface, you can develop applications and manage multiple applications, making it a more user-friendly option. Moreover, you can explore various other technologies while deploying on the cloud, broadening your knowledge of cloud technologies. In my case, the transition led to my learning of Kubernetes, enabling multi-scaling and expanding my technical skills. It was a valuable experience, and I had the opportunity to learn many new things during the migration process. I can easily rate it an eight or nine out of ten.
Rajiv Bala Balasubramanian - PeerSpot reviewer
Efficiently manages and monetizes API
It is a scalable solution. You can add more computing power to your APM gateway. It also gives you the ability to have VNet integrations with your on-prem. It is one of the leading products in the API management space. It is not just software for users but software to handle requests. For example, for a B2C e-commerce store, all requests that users make from within the store pass through this API gateway. So it is defined by the number of requests to the API gateway, not by the number of actual users who use it. If you look at the number of requests, it would be a lot from all the different systems we have within Pampers.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
"It is a stable solution."
"The solution is quite stable. We have no issues with it. there have been no crashes and we haven't experienced bugs or glitches. It's been quite reliable."
"Security is the top feature of Azure API Management."
"The API management is great."
"The stability and performance are good. It is easy to install, and it scales well too."
"I like API Management's sandbox feature. It's an environment where you can test out the API before putting it into production and connecting it to a live environment."
"It's very well integrated with the Azure environment."
"The mediation and translation from SOAP to REST technology makes it possible to open up legacy systems that couldn't be opened before."
"It is easy to use."
 

Cons

"Enterprise bots are needed to balance products like Kafka and Confluent."
"The pricing can be improved."
"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"Its queuing and messaging features need improvement."
"The initial setup is not easy."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"An area for improvement in Microsoft Azure API Management is deployment, in particular, the deployment of versions in Oryx. The development to production instance isn't adequate for me and needs to be improved. Microsoft Azure API Management lacks automation, which is another area for improvement."
"The implementation has room for improvement and can be more user-friendly."
"The solution's data mapping and orchestration are very code-intensive or require callouts to external systems."
"This solution is only available as a cloud-based deployment and it would be very helpful to have an on-premises version."
"Azure API Management could be improved with better integration with all of Microsoft's tools."
"Technical support could be more helpful and responsive."
"In the next release, Azure APIM should include deployment in various environments and CI/CD for deployment."
 

Pricing and Cost Advice

"The solution's pricing model is very flexible."
"It is an expensive solution."
"It's free for less than ten users. If you want to go beyond that, it's around $3.50 per user per month. If you want a DevOps integration, it's about $7.50 per user per month. Costs depend on the size, complexity, usage, and what facility you want to integrate. So, we use Microsoft Azure and have the entire DevOps and Visual Studio on the cloud. We get all three flavors for $7.50 per user per month."
"We are paying standard fees to use Microsoft Azure API Management."
"The product pricing is reasonable."
"Licensing fees are paid on an annual basis."
"It's pay as you go. The subscription packages have room for different scales. It's calculated by the number of apps or computers you use. You do not have to use the enterprise subscription. These subscriptions have different pricing, so you can find one to meet your needs for scalability."
"It costs around 30,000 Kronas a month, which translates to about $3,000 dollars monthly."
"Since everyone is isocentric here, it is reasonable for me."
"The licensing fees are expensive."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
851,371 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
12%
Insurance Company
9%
Government
8%
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about IBM Cloud Pak for Integration?
The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of ...
What needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...
How does Apigee differ from Azure API Management?
Apigee offers both cloud-based and on-prem options while Microsoft Azure API Management currently only offers a cloud-based solution. Both solutions are easy to use. Apigee allows for the ability...
Which is better - Azure API Management or Amazon API Gateway?
If you use Azure products, API Management is a great solution. It solves many of the problems of externalizing web services. For example, when you need versioning, establish a developer portal and ...
What do you like most about Microsoft Azure API Management?
Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation.
 

Also Known As

No data available
Azure API Management, MS Azure API Management
 

Overview

 

Sample Customers

CVS Health Corporation
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH, Opensistemas
Find out what your peers are saying about IBM Cloud Pak for Integration vs. Microsoft Azure API Management and other solutions. Updated: April 2025.
851,371 professionals have used our research since 2012.