Wednesday, November 19, 2008

The Real Cost of Amazon CloudFront

Amazon introduced web service for content delivery, called Amazon CloudFront yesterday. CloudFront is thought to be a bring a pricing war between the current CDN providers.

If you do a little bit calculations for the real cost of the CDN, it turns out that it is much higher than the advertised pricing, for smaller files.

Following is the effective cost per GB for USA locations for CloudBurst. For example - if your files are 5KB in size, you will actually pay $0.3797 per GB not $0.17 . If your file size is 10MB, then you will pay the advertised price of $0.17 per GB. So, essentially if you are distributing images or movies, CloudFront will be cost effective, however if you are distributing JavaScripts of small size, you may be paying a lot more.

File Size (KB) Effective Cost per GB
5KB $0.3797 (123% more)
10KB $0.2749
20KB $0.2224
50KB $0.1910
100KB $0.1805
500KB $0.1721
1MB $0.1710
5MB $0.1702
10MB $0.1701
100MB $0.1700
1GB $0.1700

Here is how I calculated this - for US locations, data transfer rate (for first 10 TB / month) is $0.17 and request rate is $0.01 per 10,000 requests.
Effective cost per GB = $0.17+(1024*1024/file_size * 0.01/10000);

Labels: , , , ,

Thursday, June 12, 2008

Web Service for Content Distribution Network

Having used CDN for a year now, I can say that the complexities of CDN deployment, origin server configuration, Apache configuration, pricing models, file placement, cache flush makes it pretty non-trivial deployment.

Just wondering why not have a "web service model for CDN".

Google recently introduced Google AJAX Libraries API.Google would place some of the popular AJAX libraries on their CDN servers thereby allowing caching, gzip etc. - thereby making the web pages load faster. Great idea! That could make some web pages really fast, quick to load.

Let's make CDN simple. Let's make hosting a file on CDN a 2 step process. See the following mockup:


Step 1: Upload file
Step 2:
Content type Bandwidth Requests per second


The entire process of - origin server configuration, Apache configuration, pricing, file placement, cache flush etc. can be made a 2 step process. A wrapper can be written on top of this entire process.

The pricing model can easily cover the cost of the server and the cost of developing such a web service. This could be a service on top of some of the popular CDN providers such as Panther Express, Level3, Limelight Networks, Akamai, etc.

I am surprised Amazon doesn't provide this service in conjunction with EC2 and S3.

Thoughts?

Update: Just read an interesting article - "10 Easy Steps to use Google App Engine as your own CDN". I am going to try it out, and see what the latencies look like, from different cities in the world.

Labels: , ,