Windows Azure CDN Reviews

We use the solution to reduce latency for web applications of the customers. It takes only about 200 milliseconds to respond to the request code.

The solution's Points of Presence feature works the best. It helps customers save time and maintain caching. When a user sends a cache request, it checks the nearby CDN network and responds to the cluster instead of retrieving the servers.

The next release of the solution should include configuration for the three types of cache rules: missing, predictive, and bypass.

We have been using the solution for more than two years.

It is a stable solution.

It is a scalable solution. It has been deployed in 100 metro cities.

We are already using Azure Cloud. Thus, instead of using third-party resources, our organization prefers Azure for its high resiliency, availability, and security level.

The solution's initial setup process is easy.

The solution's price is above the medium range. It is worth the value for money.

I recommend the solution to others and rate it a ten out of ten.

We use Windows Azure CDN to accelerate strategic information delivery by caching it in multiple zones worldwide.

The solution should have more capacity.

I have been using Windows Azure CDN as a customer for five to seven years.

I rate the solution’s stability an eight to nine out of ten.

I have no complaints with the solution. It is used daily worldwide.

I rate the solution’s scalability an eight to nine out of ten.

The technical support depends on the kind of contract that you have with your suppliers. If you have high contracts, you have a high response. If you have standard contracts, you can cry. If you have a good contract, you'll rate eight; if you have a standard contract, you'll rate it close to four out of ten.

We’ve used Akamai CDN before. We switched to Azure CDN because Akamai was costly and complex to apply tools. Azure CDN is easy to use.

The initial setup is complex and powerful. It will take half an hour to two hours to deploy, depending on the set of data components.

We used the standard DevOps tool to deploy the solution.

The component does the job. We will always have what you expect.

The solution’s pricing depends on installs and the kind of features you use. There is a huge difference between standard and premium.

It is important to determine the appropriate amount of data transfer, such as five gigabytes per day, based on actual needs and adapt the solution accordingly. Failure to do so may result in unnecessary expenses, mainly when dealing with sensitive or confidential information. Sometimes, people make the mistake of assuming that the most expensive option is always the best, but it is crucial to align your configuration and architecture with your specific requirements. Opt for the most suitable components based on your actual needs rather than opting for the most advanced and costly versions just for the sake of it.

Overall, I rate the solution an eight out of ten.

I use it to cache and download files quickly.

One of the most valuable aspects is the capability to store extensive datasets and objects in the cloud, enabling their download through shared access signatures.

Exploring shared access solutions with cloud accounts would be a beneficial choice.

I have been using it for about four years.

The initial setup is a straightforward process involving the creation of blog containers or file systems. It is intuitive, especially for those familiar with systems administration.

It comes at a relatively affordable cost.

I would recommend watching informative video training courses to ensure a proper understanding and emphasize the importance of implementing security measures effectively. Overall, I would rate it eight out of ten.

The most valuable feature of Windows Azure CDN is its effectiveness.

The solution’s pricing could be improved.

I have been using Windows Azure CDN for one to two years.

I rate Windows Azure CDN an eight out of ten for stability.

I rate Windows Azure CDN a nine out of ten for scalability. Most of our clients for Windows Azure CDN are enterprise businesses.

The solution’s technical support is very good. I rate the solution’s technical support a nine or ten out of ten.

Positive

I rate Windows Azure CDN a nine out of ten for the ease of its initial setup.

The solution’s deployment takes a few hours.

Windows Azure CDN is neither too expensive nor too cheap.

On a scale from one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing a five out of ten.

I am working with the latest version of Windows Azure CDN.

Overall, I rate Windows Azure CDN a nine out of ten.