Coming October 25: PeerSpot Awards will be announced! Learn more
2019-08-12T05:55:00Z
Miriam Tover - PeerSpot reviewer
Service Delivery Manager at PeerSpot (formerly IT Central Station)
  • 0
  • 47

What is your primary use case for Microsoft Azure API Management?

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

12
PeerSpot user
12 Answers
AN
Lead Solution Architect at a tech services company with 1,001-5,000 employees
Real User
Top 10
2021-05-21T09:06:22Z
21 May 21

We have two approaches to how we use the solution. We own the managed services and the other we have customers take the subscription and we manage it.

PP
Senior Solutions Architect at a manufacturing company with 10,001+ employees
Real User
Top 10
2021-04-06T13:38:19Z
06 April 21

We primarily use the solution to manage our APIs.

SK
Solution Architect at a sports company with 201-500 employees
Real User
Top 5
2020-11-10T14:58:40Z
10 November 20

We have company-wide APIs which are hosted in Niger, and some of the external clients access the applications via the API, and we provide the post-data information. The clients get their data from our larger API.

RandallMcClure - PeerSpot reviewer
Enterprise Architect at Pink Brain Technologies
Real User
2020-07-26T08:18:00Z
26 July 20

They're doing integration work between a lot of different on-premises business platforms, like Salesforce and NetSuite. We're doing integration work, but we're putting all of our APIs into the Azure cloud and using that API manager at this time.

John Liu - PeerSpot reviewer
Integration Architect at a wellness & fitness company with 5,001-10,000 employees
Real User
2020-05-13T09:16:00Z
13 May 20

We use it to manage the API. We have a backend API with service in the backend. We use API Management in the front to manage the vendors. They can do their own testing. It's quicker for us to put in the specifications so we can knock off the responses. We build the specs and then get an external developer to start the development without the web service being ready. We also use it for the security and for the clock in features.

KH
System Analyst at a tech services company with 51-200 employees
Real User
2020-04-01T07:25:00Z
01 April 20

Our primary use case is to provide API mapping for our clients. We're a customer of Azure and I'm a system analyst.

Learn what your peers think about Microsoft Azure API Management. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
633,952 professionals have used our research since 2012.
MB
Enterprise Infrastructure Architecture at a tech services company with 1,001-5,000 employees
Real User
2020-03-22T06:49:13Z
22 March 20

Our primary use case is for managing internal APIs, for ordering process APIs and in general process APIs, and resource manipulation APIs. We need an API management to get a better overview, and this is one use case with analytics parts. Another use case is security, being able to rotate API keys and to manage access at a signature point. Finally, we also have the developer portals with the self-service capabilities so that developers can request access to APIs through a developer portal and manage their own keys. We are still in the ramp-up phase, so currently we have actively two or three guys using it. We're planning to increase usage. We're in partnership with Microsoft and I'm an enterprise architect.

Srinivas Kode - PeerSpot reviewer
Vice President - Competency and Channels at Techwave.
Real User
2020-03-09T08:07:46Z
09 March 20

It's more of a subscription driven consumption based model, where the APIs are developed to connect backend ERP systems such as SAP and deployed into a library for consumption by both internal and external consumers. The APIs are exposed to the consumers that get onto the API gateway and identify the needed API from the library, use the instructions to subscribe, quickly test and connect to the backend SAP to get the expected information/transaction processed. Prior to this solution there was an age old EDI interface solution. This is enabling the customers to be more flexible with their integration architecture and be more agile as it reduces the IT integration dependency and provides a better user experience. This is part of Techwave application modernization strategy to bring solutions that can bring agility and flexibility to customers and be able to decouple business with huge IT dependent solutions. This is helping us to help our customers migrate away from the age old EDI technology to the latest API and microservices based architectures.

Anurag-Bhatnagar - PeerSpot reviewer
Principal Consultant at a tech services company with 10,001+ employees
Consultant
2020-02-09T08:17:01Z
09 February 20

We are publishing microservices using API management. We have created various packages and policies that we are applying over there. We have also created a portal for developers so that they can see what we are doing.

Nagesh Paramesh - PeerSpot reviewer
Head - Data & Digital Service line(s), BFSI Cluster at slk software
Real User
2020-01-12T12:03:00Z
12 January 20

We are a software firm and this is one of the solutions that we provide for our customers.

it_user1221840 - PeerSpot reviewer
Managing Director at Ebiz consulting gmbh
Real User
2020-01-12T12:02:00Z
12 January 20

We use the product for managing APIs - for internal as well as for external communication. Furthermore we enable transparency, governance and re-use.

Luís Silva - PeerSpot reviewer
Manager at Ginkgo Management Consulting
Real User
Top 5Leaderboard
2019-08-12T05:55:00Z
12 August 19

We use the cloud model. Our primary use case is for integration between different systems. There are many use cases for the API management tool, but the most common scenario is integration between different systems.

Related Questions
Netanya Carmi - PeerSpot reviewer
Content Manager at PeerSpot (formerly IT Central Station)
Nov 01, 2021
Why?
See 1 answer
01 November 21
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 subscription keys. It provides a good UI for developer portals. The developer can register, request, and manage subscriptions easily in the portal. Another thing we liked was the high level of customization. You can use API Management for back-end APIs. You can place the APIM in front to give extra layers of security. APIM is great for lift and shift migrations, too, by fine-tuning the policies in the APIM. The downside is, first, the cost. You need to pay up front for the service. So if you are a small business, it can be expensive because the cost increases with each API. If you are already using Azure, you need premium Azure B2C to integrate with your system. AWS API Gateway (API GW) might be better for organizations that already use other AWS resources. It is a great tool for web services development. If you need to integrate external tools, AWS API Gateway provides an extra security and authentication layer for front-end web services. For instance, as an HTTP front end for internal resources. We use API GW for front-end web services and to integrate static resources. Although we are overall happy with API GW in terms of security and rapid development, it leaves some room for improvement. If you need to create a private API, it can be very difficult. Certifying clients can be a hassle, as well as trying to debug multiple services. Conclusions Azure API Management is a strong solution for large organizations, particularly if leveraging Azure products already. AWS API Gateway is more versatile and the pricing is better.
Nurit Sherman - PeerSpot reviewer
Content Operations Manager at PeerSpot (formerly IT Central Station)
Mar 23, 2018
One of the most popular comparisons on IT Central Station is Apigee vs Mulesoft Anypoint API Manager Which of these two solutions would you recommend and why? Thanks! --Rhea
2 out of 7 answers
it_user521277 - PeerSpot reviewer
Technical Lead at hcl
22 March 18
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.
it_user783168 - PeerSpot reviewer
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). Best Regards, Arnab.
Download Free Report
Download our free Microsoft Azure API Management Report and get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
DOWNLOAD NOW
633,952 professionals have used our research since 2012.