Azure API Management vs. Azure App Service

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

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

Incentivized

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

Incentivized

• It has options to deploy using CI/CD.
• It has great integration with Azure Devops
• It has all the common runtimes, so we don't need to install softwares.

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

• the learning curve can be tough (just like other azure services)
• the UX/UI could be more intuitive (just like other azure services as well)
• monitoring can be hard to understand
• Microsoft's learning resources are hard to understand

Incentivized

We had an issue where we deployed too large of a resource and didn't notice until the bill came through. They were very understanding and saw we weren't utilizing the resources so they issued a generous refund in about 4 hours. Very fast, friendly, and understanding support reps from my experience.

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

Azure has many data center, their services are more reliable. Azure has way more features than both Linode and DigitalOcean. If someone wants a complete reliable service, he/she must go to Azure instead of Linode and DigitalOcean because even though azure charges more, it is worth the money you pay there.

Incentivized

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

• Reduced the deployment time of ASP .NET applications in the company.
• Gave us an alternative to quickly deploy our applications without granting access to the version control system to a third platform.

Incentivized