Akamai offers their API Gateway, touting easy control and access to enterprise applications via their services.
N/A
Azure API Management
Score 8.0 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
Lightweight and serverless version of API Management service, billed per execution
Pricing
Akamai API Gateway
Azure API Management
Editions & Modules
No answers on this topic
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
Offerings
Pricing Offerings
Akamai API Gateway
Azure API Management
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
Akamai API Gateway
Azure API Management
Considered Both Products
Akamai API Gateway
Verified User
Anonymous
Chose Akamai API Gateway
Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other …
Apigee is by Google and seems to be promising. The cost seems high though. With Azure, we do not have to make any special purchases. CapEx vs OpEx! But, Apigee could be more environment independent compared to Azure APIM. The promise of speed by Apigee is also better compared …
It’s a great tool, and so easy to seamlessly connect into your current Azure world that it’s hard not to look at it or even test the waters with it. It’s priced well, and is feature-rich enough to accomplish most tasks. I think the ease of having everything together and the …
It is really helpful for managing [the] scaling of systems with need and utilizing resources when needed. Also, DevOps support for deployment plans is quite useful when deploying applications. Monitoring systems with graphQL and utilizing them in APIs is quite helpful when used in Microservices systems to identify system capabilities and user utilization of applications.
The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.
Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.
Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other aspects. Also, [a] user-friendly system helps people to handle [the] system with necessary options
Decrease in time required for deployment and monitoring by significant amount causing less support resources needed
Scaling applications on month-end at high usage time has reduced TAT time for issues and no of issues occurring
Quota enforcement has allowed [managing] multiple systems and their needs in respective stakeholders hands and reduced infra teams involvement in [the] management of reoccurring problems
It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.
