Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Azure App Service
Score 8.7 out of 10
N/A
The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
$9.49
per month
Pricing
Azure API Management
Azure App Service
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
Shared Environment for dev/test
$9.49
per month
Basic Dedicated environment for dev/test
$54.75
per month
Standard Run production workloads
$73
per month
Premium Enhanced performance and scale
$146
per month
Offerings
Pricing Offerings
Azure API Management
Azure App Service
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Free and Shared (preview) plans are ideal for testing applications in a managed Azure environment. Basic, Standard and Premium plans are for production workloads and run on dedicated Virtual Machine instances. Each instance can support multiple applications and domains.
More Pricing Information
Community Pulse
Azure API Management
Azure App Service
Considered Both Products
Azure API Management
Verified User
Professional
Chose Azure API Management
N/A
Azure App Service
Verified User
Employee
Chose Azure App Service
AppServices that's easier to manage than its competitors, specially if you have everything in Azure. But also that's the most expensive service when you escalate or start using it for massive data processing. It would be an excellent containers platform if were easier to deal …
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.
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.
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.
I enjoy the fact that Azure App Service can be managed by the Azure portal and a fully graphical user interface, as well as from two different flavors of command-line interface, i.e. Azure CLI and Azure Powershell. By utilizing the Azure Cloud Shell, we are able to switch between Azure Bash (CLI) and Powershell at any given moment and manage the Azure App Service settings from devices of any form-factor (Web based management).
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.
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.