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.
