Cloud = "That service/infrastructure/platform that you need that will be hosted by someone else in their data center"
If we wanted to be precise, we could refer to it as "Storage Clouds", "App Server Clouds", "Database Clouds", etc...
“We’re working with AWS to provide an Elastic Beanstalk Ruby on Rails container that leverages the optimized Engine Yard stack which has been battle-tested by thousands of high-growth companies.” John Dillon, CEO of Engine Yard
http://www.businesswire.com/news/home/20110119005591/en/Amaz...
Now, Amazon may start siphoning off python users that switched to rails just to use Heroku.
a lot of "cloud" services these days are nearly identical to VPS services of yore, with the added new ability to create/destroy VPS nodes whenever you want. very few of the big "cloud" providers actually handle auto scaling (as it's difficult in a world where all apps are not made the same).
You can do this with EC2. You can set up monitors based on CPU usage over a time period and it'll start new nodes if required.
S3 is 'autoscaling' for serving files. Just upload your files and pay for what you use.
a "true" cloud would just handle all that stuff transparently.
Be wary of leaky abstractions.
http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
From what I'm reading, Beanstalk changes this and clearly puts AWS in the category they've long claimed to be in. Not that their service wasn't great/unique before. This just puts them that much further ahead.
It's along the lines of what Heroku does with their routing mesh layer (as far as I understand it).