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 …
Akamai and CloudFlare are leaders in the CDN and Security sectors. Akamai has a very strong capability and execution in terms of enterprise services. Their offerings are are somewhat similar in some aspects but there is no products in the respective markets that compares to …
We have limited software developers and don't have the need for a big cloud service provider along with their costs. Google Cloud CDN brings to usr, reliability and brand familiarity. Google Cloud CDN also doesn't bother us with pitches or 1000 emails about the products. We …
AWS is definitely cheaper than the Google Cloud platform for VM instances. In terms of progression, it is clear that Google Cloud is making significant improvements to the platform. Google Cloud offers the option of a free tier on a wide range of their products. It gives you a …
It has More transparency in pricing as well as more services at a lower cost. The ability to stream video and other specialized features, and the ability to manage all projects can be accessed through a separate creative dashboard. The initial setup is very simple and you can …
We are already using Google Cloud for our infrastructure needs, so it felt like a natural extension to use. We were earlier using AWS CloudFront and some workloads were using Cloudflare. Though to centralise everything, we moved them to Google Cloud CDN. This helps in easier …
Fastly was having minimum spend system, when we started using it, and the pricing structure didn't fit our budget, so we decided to change the provider. Also, compared to Google Cloud CDN it was a little bit difficult to set up and use for beginners.
Google Cloud CDN works really well for a reliable CDN service, especially when used with other Google Services. It is highly reliable, efficient, and speedy. That said it can also be difficult to implement and lacks some support services found with other CDN services. It …
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.
Google Cloud CDN is available globally and supports various load balancers available in different regions around the globe, so I find Google Cloud CDN as one of the best choices for CDN as it serves globally and it is really fast, safe, and secure. It might be not suitable for you if you do not have any technical background.
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).
There is not really an interface for managing rules directly, compared to market leaders, Google's implementation is probably strong on the technical side but for the average user it might be lacking. There are no advanced features which can be compared to what other leaders in the CDN sector are providing or they can be achieved but with high implementation cost and usage of other products in the Google Cloud suite
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.
I didn't have the need to use support from Google when I was either testing or setting up my website. Information was easily found by searching online if I needed to, and the options that I needed to install or enable were there on the setup page. Honestly, I was a former systems administrator so most of this stuff is not challenging for me.
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.
We have limited software developers and don't have the need for a big cloud service provider along with their costs. Google Cloud CDN brings to usr, reliability and brand familiarity. Google Cloud CDN also doesn't bother us with pitches or 1000 emails about the products. We went and signed up for it, without dealing with a pushy salesperson.
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.