This reminds me… I need to set up my own AWS testing account to try a few things.
Also, sharing because I laughed at “persistence”. For reference, in these terms “persistence” may as well equal “stagnation”.
Original Post from David Federlein: This also applies to Eucalyptus, or any cloud build. Seriously, if you’re using your cloud as a vps host, you’re not actually doing anything but virtualized infrastructure and you’re missing the point.
Quote:
When competitors like Rackspace argue “persistence” as a competitive advantage, they’re missing the entire point of AWS. EC2 is the antithesis of buying a server, lovingly configuring it into a unique work of art, and then making sure it doesn’t break until it’s depreciated off the books. Instead, EC2 instances are intended to be treated as disposable building blocks that provide dynamic compute resources to a larger application. This application will span multiple EC2 instances (autoscaling groups) and likely use other AWS products such as DynamoDB, S3, etc. The pieces are then glued together using Simple Queue Service (SQS), Simple Notification Service (SNS), and CloudWatch. When a single EC2 instance is misbehaving, it ought to be automatically killed and replaced, not fixed. When an application needs more resources, it should know how to provision them itself rather than needing an engineer to be paged in the middle of the night.
How does an Amazon EC2 instance differ from a traditional server? It’s all about service-oriented architecture.
Original G+ Post