Azure CDN vs. StackPath Edge Delivery

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.

Incentivized

It is great as a primary or backup CDN. We have had no issues with performance. The cache hit ratio is high. Some of the options are hidden within the API and you have to configure them with API calls, such as configuring signed fetch requests to an S3 origin. These should be in CLI or Web Console. The deployment of edge side scripts with the CLI or CI/CD could be improved.

Incentivized

• New websites can be boosted up quickly
• Easily scalable according to our performance requirements
• Easy integration with other Azure services
• You only pay for what you need

Incentivized

• Price competitive.
• Easy to use.
• Good reporting.
• Quick to deploy.
• Start-up friendly.
• Good technical information via blog, FAQ and community discussion.
• I can talk to real person for urgent support.

Incentivized

• 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).

Incentivized

• Analytics.
• Many options hidden in API.
• Web console.

Incentivized

I give it 9/10 rating because it solved my problem by Caching my website content on global servers to load faster.

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.

Incentivized

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.

Incentivized

1. Total solution (CDN, WAF, monitoring, DNS hosting) which offers me a turn-key solution.
2. Power customer portal which empowers to configure my service performance.
3. Clear and granular service packages that meet my budget.
4. They provide in-person real-time communications which can provide me urgent support.
5. They offer start-up friendly program.

Incentivized

• 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.

Incentivized

• Easy 25-30% improvement in website performance vs non CDN solution
• Less expensive and faster object storage than AWS
• Aided greatly in maintaining KPIs in terms of performance, availability

Incentivized