Microsoft offers a content delivery network, Azure CDN.
N/A
Fastly Edge Cloud Platform
Score 8.0 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.
Well, Azure CDN is a reliable and user-friendly content delivery network. Additionally, it performs multiple tasks that helps us in website management.
We did not evaluate any other CDN solution because we choosed Microsoft Azure as our cloud provider, so the Azure CDN choice was easy. Furthermore, the speed at which we managed to stand up the CDN and push content in it was very appreciated during our website development, so we …
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 …
Azure CDN is certainly the favorite when you're already working in Azure like us. CloudFront has programmability and should obviously be considered first if you're already on AWS. I've seen use of CloudFlare for one-off sites (EG, my friends who are WordPress people and are …
We did not evaluate any other CDN's before we selected Azure. We heavily use Azure for our development and infrastructure efforts so choosing the Azure CDN was easy. The only thing we compared it to was standing up a Windows Server VM and pointing a CDN URL to it allowing it to …
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.
For the longest time they didn't have a robust SDK. They have one now, but it could be better.
The different flavors of Azure CDN (Akamai, Verizon, etc) have different costs, but not well differentiated features. Might be confusing to new users.
I'm not overly familiar with it, but AWS does have a programmability in their CDN offering (Lambda @ Edge) and Azure doesn't seem to have an equivalent (Azure Functions is region-specific).
Fastly Edge Cloud Platform is a powerful tool with robust capabilities, but it requires deep technical knowledge to integrate effectively into existing applications. While its performance and features are excellent, the lack of a user-friendly interface and the need for advanced configuration can make it challenging for teams without experienced developers.
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.
We did not evaluate any other CDN's before we selected Azure. We heavily use Azure for our development and infrastructure efforts so choosing the Azure CDN was easy. The only thing we compared it to was standing up a Windows Server VM and pointing a CDN URL to it allowing it to serve as a file server, which was much more cumbersome.
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 the edge, meaning that, for example, quick authorization checks can be handled without having to work with the origin server.
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.
While I was at Wanelo we were able to put Fastly in front of the growing web app, and selectively cache end points to improve stability and performance. In the meantime we rewrote the app completely in Ruby. We wouldn’t have been able to do that without Fastly.