Azure API Management vs. Azure Virtual Network

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.

Incentivized

For SAAS it's not required but for most of IAAS and PAAS components Virtual network are required the deployment of storage account doesn't require virtual network .

Incentivized

• Easy commissioning of APIs.
• Great policies to control access.
• Easy mock services for testing.

Incentivized

• Allows connectivity within Vnet
• Secure Communication can be established
• Security Rules can be enforced
• Routing Can be Established

Incentivized

• 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.

Incentivized

• Integration of Express Routes needs to be simplified
• Endpoints Security has to be available in Vnet itself

Incentivized

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.

Incentivized

During Initial Phase itself on cloud Journey Azure Services was opted for there was no comparison done

Incentivized

• We can always think of positive ROI impact on business
• It helps to easily facilitate the design, deployment, and maintenance of our APIs

• Deployment of Gateway needs to be faster as it takes a lot of time which is negative

Incentivized