In the end, I learnt it the hard way, Amazon s3 is rubbish and i wouldn’t recommend it to anyway. Reporting & statistics is crap, customer service is not good (no telephone & i emailed them twice and still didn’t get a reply) Plus i don’t think they protect against spam which i believe is the cause for the majority of bandwidth.

Guess i learnt the hard way, not to use pay as you go like S3. Unlimited bandwidth is the future. I had to delete all my files from s3 and shut the site temporarily. nearly caused me to go bankrupt

I’d like to know more about the technical implementation, what plugins were used, code changes required and whether there are exceptions to the rule (are all WordPress static files also being stored on S3, etc).

Namely, if someone wanted to achieve the same where should they start and what pointers would you give?

http://tantannoodles.com/toolkit/wordpress-s3/

However we no longer worry about storage capacity on the file servers, we have way more redundancy and I/O in each datacenter (for hot files) with no complicated cross-datacenter failovers, and maintaining the cache servers is easy. They’re quickly interchangeable. I feel that overall user file serving, which is a pretty crucial part of our service, is overall more reliable. I’d feel more comfortable doing things that increase storage usage now.

So right now it’s costing more than double what things used to cost, and is slower for uncached files, but I think as we tweak the caching we’ll get a higher hit rate and get the bandwidth cost down, which is 95% of our S3 cost.

We was thinking about S3 as our new primary storage server (we are serving actually more than 5000 slightly more than 4 or 5 GB) but we stuck on the implementation, and decided to work on this later this year… I’d love to know better some insight, just to not reinvent the wheel

Apart from that, I think that wordpress.* is often a notable resource for testing and promoting technologies, and let even us little coders know something new.

This community workflow is just amazing. Keep up this good work, and thank you!

I am honestly surprised by the assessment that you are not saving money, especially given SmugMug’s now famous report on how it has saved them money. At the rate WordPress.com must produce content aren’t you constantly adding more storage? And doesn’t that hardware degrade and depreciate over time?

You are really losing money right? Your AWS bill may have gone up, but surely you are now saving money in other areas right?

Terribly Curious,
Byrne

Darin

In the Amazon newsletter they promoted Content Spooling Network as a good use of their services.

Akismet has caught 232,946 spools for you since you first installed it.