Got email from CDN77. It announced that API 2.0 released.
Much more API features are now available. We worked hard so that we could give a positive answer to your most frequent questions:
“Can I create / edit / delete a CDN resource through API?”
YES! You can manage your CDN resources (incl. Live Streaming) easily with API.
“Can I integrate the reports to my internal tools using API?”
YES! All the data we provide you with in the Reports section + Logs are now reachable through API.
“Can I make changes to my account via API?”
YES! You can edit all the account details including the billing and invoicing section.
More details of API 2.0, check the Documents.
I start to use CDN from April 2010, with MaxCDN. Later, I moved to Amazon, FrontCloud in August, 2010.
For some reason, I move back to MaxCDN. I start to use MaxCDN again from June 2012. In April 2013, I started to use CDN77.
A few days ago, in March 2014, I go back to Amazon AWS CloudFront. It is a reliable CDN service provider. The price is pay as you go. Based on my network volume, I prefer this price structure.
I setup CloudFront with custom origin server. Add CNAME on it. One of the CDN rules is to use two CDN host name, not one, not three. Two is the perfect number and best performance.
I tested my new CloudFront CDN ping value through CA ping tool. There are over 30 monitoring stations worldwide. My testing result is:
It shows that CloudFront has better ping value.
The original testing data link.
Testing tool provided by CA Technologies. http://cloudmonitor.ca.com/en/ping.php
Continue reading “Go back to Amazon AWS CloudFront”