21–30 of 39 posts
While S3 might be "extremely durable" from a technology standpoint, its unceremonious dumping of Wikileaks as a customer shows it to be politically fragile. You might think of Wikileaks as "extreme," but this is an organization that was neither convicted nor even charged with breaking any laws, which Amazon dumped as a customer on very vague TOS grounds following pressure from Sen Joe Lieberman. This could be an issu…
While S3 might be "extremely durable" from a technology standpoint, its unceremonious dumping of Wikileaks as a customer shows it to be politically fragile. You might think of Wikileaks as "extreme," but this is an organization that was neither convicted nor even charged with breaking any laws, which Amazon dumped as a customer on very vague TOS grounds following pressure from Sen Joe Lieberman. This could be an issu…
The technology is good, but sometimes it's not about the technology.
Coming from the CTO of Amazon...
Do you mean that in a "he's clearly just promoting S3" or a "woah, the CTO of Amazon has time to code neat tools" kind of way?
S3 are kind of his "servers" no ;)
Earlier quoted context omitted.
Do you mean that in a "he's clearly just promoting S3" or a "woah, the CTO of Amazon has time to code neat tools" kind of way?
It doesn't sound like he coded all that much from the post. He even mentions that Cactus is a little bit too much work since there's not much of an existing community surrounding it. I was just surprised that it was the CTO of Amazon after I read the post. S3 are kind of his "servers" no ;)
The extension and plugin mechanisms will make it easier for me to start adding my own code without having to modify the core framework. But it is always more fun to add these kind of things if there is a community to give you feedback.
If you go to the bottom of the page at http://allthingsdistributed.com/ , you'll see that the blog actually requires "Movable Type Pro". AWS doesn't provide a way to serve from S3 without the help of a CNAME redirect, which means that you're out of luck if you want to use the Jekyll+S3 setup with a naked domain name (naked, as in no "www" or "blog" subdomain). And it also means that you're going to have to get some o…
Do you even really need S3 if you're just serving up static pages? A $5/mo web host or a VPS slice would probably be overkill - you're not hitting a database at all.
If you want to get really exotic, you can check out the Haskell version of this tool. My site ( http://dave.fayr.am ) does the same thing using Hakyll and S3. You can see the code here: https://github.com/KirinDave/public-website
While S3 might be "extremely durable" from a technology standpoint, its unceremonious dumping of Wikileaks as a customer shows it to be politically fragile. You might think of Wikileaks as "extreme," but this is an organization that was neither convicted nor even charged with breaking any laws, which Amazon dumped as a customer on very vague TOS grounds following pressure from Sen Joe Lieberman. This could be an issu…
Not entirely sure what the issue was, since I use S3 to host static assets for other sites that see similar traffic levels, and haven't gotten any 503 errors. And clearly ATD seems to be handling the HN traffic just fine.
Here's the code: https://github.com/ohrite/vacation Here's the gem: http://rubygems.org/gems/vacation
If you want to get really exotic, you can check out the Haskell version of this tool. My site ( http://dave.fayr.am ) does the same thing using Hakyll and S3. You can see the code here: https://github.com/KirinDave/public-website
I also threw together a script (./publish) that first gzips the static files and then uploads them to S3 with the correct headers (gzip and cache-control). Finally, it invalidates the old files on Cloudfront. Combined I get a very fast site, while keeping the cost low. Again, you can find it all in the github repository.