News for hackers. Stuff that matters.

A comment on Distribute Your Content With Amazon CloudFront.

Re:Distribute Your Content With Amazon CloudFront by Tichy on Tuesday November 18, 2008 @06:54AM (#368150)
OK, dumb question, but I thought there was this thing called Apache HTTPD that was traditionally used for serving static content? What ever happened to that? Granted, it has one basic flaw, in that it doesn't deliver usage statistics of my site to Amazon, but other than that?
[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by rmaccloy on Tuesday November 18, 2008 @07:04AM (#368155)
Serving static content from Apache or lighttpd is trivial.

Putting multiple boxes hosting that httpd in various geolocations, setting up DNS and BGP to route users optimally, designing failover routes and keeping N nodes in sync is the hard part.

[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by Tichy on Tuesday November 18, 2008 @12:40PM (#368452)
True, but when does one reach a size (user base) at which stuff like that becomes critical?
[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by emmett on Tuesday November 18, 2008 @01:06PM (#368483)
The same size one should start using any CDN - as soon as you start caring about page load speed.
[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by Tichy on Tuesday November 18, 2008 @02:53PM (#368624)
OK, I forgot about that problem (I assume it is the limitations of browsers to two connections per server at a time).
[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by wmf on Tuesday November 18, 2008 @04:05PM (#368725)
You can work around that with multiple hostnames, but lower latency is still better.
[ Parent | on HN ]
Re:Distribute Your Content With Amazon CloudFront by tlrobinson on Tuesday November 18, 2008 @05:58PM (#368867)
And latency. And bandwidth.
[ Parent | on HN ]