Here some thoughts about my recent experience with CDN. Actully I it twice in my life for two project. First time it was CloudFlare, and another one is hard to call CDN solution but it was GEO IP caching node built on Nginx, to provide better ping in Russia. Definelty tiny experience, until I was asked to make the review and to find CDN solution for one of the game portal www.sevelina.com. This was quite challenging due to this project is quite heavy load and I’ve spent on it enough time for optimization, so the customer decided to request my service again.
So after reviewing and following the suggested budget I’ve ended on two candidates Amazon CloudFront CDN and Cloudflare. Both give opportunity to try for free, and both look well-known. As for Amazon Cloudflare CDN I was familiar with, I’ve put the test for on week and review it for 5 days. And I found it exactly what I was looking, but I wish to provide some digits and explanation to my customer and tested for 1 day with Amazon CloudFront CDN. To be honest it was disappointing experience. First of all registration, money demanding registration, no bank card, no service to try. Another thing, which is not statement but my thoughts, that you should use 2 other products from Amazon to have successful CDN service: Route 53 (Amazaon DNS service) and Amazon Store EC2. You still have the opportunity to try it, and that what I used for testing, some junky path redirected link to the requested web which should be distributed over Amazon CDN.
So in total I wasn’t happy but decided to finish my small reviewing and here the figures. The main server located in NY, North America. I’ve used just-ping.com service, same while I was testing CloudFlare, which gives ping time in ms from various locations around the world, and here what I found:
|Location||Cloud Flare||Amazon CloudFront|
|New York, U.S.A.:||5||4.4|
|Santa Clara, U.S.A.:||5|
|London, United Kingdom:||3||1.8|
|Hong Kong, China:||2.8||4.7|
|San Francisco, U.S.A.:||12||8.6|
|Auckland, New Zealand:||24.2||24.3|
|Manchester, United Kingdom:||8.6||18.6|
|Kuala Lumpur, Malaysia:||192.1||7.1|
|Cape Town, South Africa:||150.6||340.7|
|Glasgow, United Kingdom:||1.3||9.2|
|Buenos Aires, Argentina:||129.1||29.7|
|Sao Paulo, Brazil:||107.1||2.2|
|New Delhi, India:||111.1||76.7|
Amazon CloudFront vs Cloudflare. Which CDN service to use.
|Ping almoast equal|
|Ping is faster|
I suppose this color marks will ease the reading of this table, but in general it is clearly visible that it is almost similar with some benefits in various locations, which were not priority for my customer. Take on the top the simplicity in registration process, complete free access the Cloudflare service, and deadly more simple setup. I’m very happy that this service exists, and I recommended my customer to subscribe for paid service, to have ability to communicate in case of disaster. Keep in mind that Amazon specially charge for support, and support is not included in their price plan.
I hope it will help you with your first step into CDN using process.