Microsoft offers a content delivery network, Azure CDN.
N/A
Fastly Edge Cloud Platform
Score 7.1 out of 10
N/A
Fastly, headquartered in San Francisco, offers the Fastly Edge Cloud Computing, Content Delivery Network (CDN) (formerly Fastly Deliver@Edge). Priced by bandwidth in gigabytes and number of file requests, Fastly supports image optimization, video and streaming, load balancing, and cloud security via web application firewall (WAF) and DDoS protection. Additionally, Fastly is available as a managed CDN.
$0
per 10,000 requests
Pricing
Azure CDN
Fastly Edge Cloud Platform
Editions & Modules
No answers on this topic
Requests
$0
per 10,000 requests
Next 10TB
$0.08
per GB/per reigon
First 10TB
$0.12
per GB/per reigon
Offerings
Pricing Offerings
Azure CDN
Fastly Edge Cloud Platform
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
—
—
More Pricing Information
Community Pulse
Azure CDN
Fastly Edge Cloud Platform
Considered Both Products
Azure CDN
Verified User
Director
Chose Azure CDN
Azure CDN is very similar to other CDN choices -- we generally choose it when the decision to deploy with Microsoft Azure has already been made and the software architecture requires a CDN. Because Azure CDN is very similar to choices from a number of other vendors, we usually …
Fastly is a great choice for CDN vendor when performance and has the ability to quickly invalidate an asset from all POPs very quickly. It shines in use cases that require media delivery, like video. Fastly also provides a highly-optimized way to handle logical operations at …
Azure CDN has at hand an infinity of applications and tools to implement in your system and have better control of your data in a clean and secure platform on the web, we recommend this program since the percentage of solutions provided by this program is very high and find a way to make each user's job easier.
The service is really well-suited for pretty much any site that is primarily display-driven (that is, mostly GET requests). The network is able to handle massive volumes of traffic and their POPs have spread out pretty much anywhere that it's easy to get them (so basically everywhere but China and Russia). My team witnessed several large-scale attack attempts on some high-profile websites (attacks in the 10s of millions of requests per second) that were mitigated before ever coming back to the actual application; in one case we didn't realize the attack had happened until we looked at the logs the next day. Because it's a cache store option, the default configuration does not cache POST responses, and it can be difficult to set up things like authenticated paywalls as a result.
I found the CDN very easy to setup and configure within the Azure Portal.
Being Azure, there are plenty of free tools that allow you to manage the CDN from a UI that is not the portal. This was especially handy when I trained end users how to manage content within their specific realm.
Great support from the team whenever we're stuck. Very proactive in resolving issues and also making changes as per the requirements of the organization.
Azure CDN reduced origin instance load by removing the need to constantly serve large numbers of static files, meaning applications can be deployed with smaller/fewer instances.
Azure CDN reduces apparent load times to customers by serving cached files out of POPs in the local region of those clients, instead of requiring those clients to make multiple, lengthy requests through to the origin servers.