Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Azure Monitor
Score 8.6 out of 10
N/A
Microsoft's Azure Monitor is designed to analyze and optimize the performance of web applications and infrastructure, including virtual machines (VMs), Azure Kubernetes Service (AKS), Azure Storage, and databases. Monitor Linux and Windows VMs and their health and dependencies—all on a single map.
$2.76
pay as you go per GB
Pricing
Azure API Management
Azure Monitor
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
Pay-As-You-Go
$2.76
per GB
100 GB per day
$219.5
2 per day
200 GB per day
$412.1
6 per day
300 GB per day
$604.8
0 per day
400 GB per day
$788.4
8 per day
500 GB per day
$968.8
0 per day
600 GB per day
$1,904
per day
700 GB per day
$3,718
40 per day
800 GB per day
$9,016
per day
Offerings
Pricing Offerings
Azure API Management
Azure Monitor
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure API Management
Azure Monitor
Features
Azure API Management
Azure Monitor
API Management
Comparison of API Management features of Product A and Product B
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.
We were able to get a single pane of glass for all our monitoring needs on Azure Monitor. However, we would like to see it improve to auto scale out and scale in depending on the load without human intervention. This can help us get to the No Ops model and rely on automated processes rather than manual intervention.
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 have not had to work with Azure Monitor support, so it is difficult to say how well the support team is. I assume that Azure has a well-versed team on the customer service side to assist with any issues customers may have. I may need them in the feature.
While other tools have their own unique capability, Azure Monitor helps us monitor essential PAAS services that are not supported by other tools. So even though we have one other APM tool, we still rely on Azure Monitor for some of the special PAAS services, this is a huge advantage.
