Akamai Technologies, headquartered in Boston, offers Akamai Connected Cloud, a content delivery network (CDN) with a variety of services used to guarantee application, API, and media delivery.
N/A
Azure API Management
Score 8.7 out of 10
N/A
Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Pricing
Akamai CDN
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 CDN
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 CDN
Azure API Management
Features
Akamai CDN
Azure API Management
API Management
Comparison of API Management features of Product A and Product B
Akamai is a well-established brand name with a great product. It meets and many time exceeds the needs for global content delivery and security management layer at the edge. Fine grain security tuning seems cumbersome as the definition of the app keeps changing. It also requires an investment of time for the setup which doesn't necessarily make sense for smaller scale scenarios. Some products offered by AWS, Azure or the Google Cloud can be more tightly integrated with cloud provider offerings thus easier to configure.
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.
Content offloading - once rules are set up within Akamai you don't need to even think about how many images or large JavaScript or CSS files (for example) are being served from your own estate, Akamai takes care of it all via rules that are quick, easy and flexible.
Page caching - for pages that don't change very often Akamai allows you to set up rules, quickly and easily, to serve up your page content for you, which takes even more load away from your origin servers.
Quick rollback - the Akamai system allows easy testing of rules and changes via a staging system, and also offers a quick rollback option, which is perfect for the rare occasions when something has been set up incorrectly.
The interface in their control centre could be a bit more user-friendly with some of the settings in places that you wouldn't expect them to be. The search offsets this problem to an extent but it's still sometimes slower than you'd like to find what you are looking for.
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.
Their support documents are excellent and provide a lot of useful information for all their services. The only reason I didn't give them a 10 is that the time it takes for them to respond to an issue could be slightly faster.
We've used -- and considered -- a whole number of CDN offerings. The good news is that almost all of the CDN products on the market are terrific, and will pay for themselves via increased customer satisfaction and lower monthly hosting bills. For some cases, we're still more likely to suggest CloudFlare (which has a free tier) or an integrated offering from a cloud provider, like Cloudfront.
Akamai RoI improved over a period of times since it comes with heavy costs, however global deliveries in over 100 counties and global web platforms usage helps improve RoI
With the complex UI challenges, ROI could be impacted negatively when you have to invest in operations and time.