Yeah, I am gonna go ahead and have to disagree with that. Non-statistical personal experiences are worth just about as much as opinions.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
We moved our development and production systems to AWS in 2008 and have been quite happy. It has allowed us to grow and scale with load on production and quickly test things in development. There a few things to keep in-mind. First, if you know your usage pattern and can drop some money upfront then utilize the reserved instances to save some money. Second, you will need a script management system of some kind to run on the virtual servers at boot/shutdown, I recommend using something like Rightscale or Scalr. Most importantly, don't do it without some experienced help for the setup, a day of a consultant's or system admin's time to walk through your migration plan with you will save you a lot of help down the road. Lastly, aws has a cost estimator that is quite helpful.
Wonder if i can cut 1k somewhere to make it 66.6k just for fun.
Its a personal site, with just a picture of me, and lots of text. Runs Drupal 7 theme based on Stark.