3 ms·
What about the amount of dev time and sysadmin needed to fully use each option? If you want to take advantage of AWS for spiky use, you need to automate the he
by autarch 15y ago
What about the amount of dev time and sysadmin needed to fully use each option?
If you want to take advantage of AWS for spiky use, you need to automate the heck out of starting and stopping instances, redistributing requests to new machines, etc.
Horror stories about EBS make me think that you'd better reconsider storage if you're hosting everything with AWS too.
Of course, the flip side is that with a totally self-hosted system, you'll probably need more sysadmin work, and you may end up spending money on things like remote hands when a drive fails or a network card dies.
Then there's managed hosting. You don't have the super awesome scaling magic of AWS, but you don't have to deal with the physical bits much either. And you still get real physical hardware attached directly to each system when it comes to storage.
I think that really understanding the costs is a lot more complicated than this article suggests.
- yummyfajitas 15y agoIf you want to take advantage of AWS for spiky use, you need to automate the heck out of starting and stopping instances, redistributing requests to new machines, etc. The thing is, this is not difficult to do with AWS: $ ec2-run-instance ami zone --user-data-file spin-up-a-new-webserver.sh ...(you need to parse this for the instance id)... $ elb-register-instances-with-lb $LOAD_BALANCER --instances $INSTANCE_ID (In real life, use Boto (Python) or equivalent in your language.) Once the new instance comes online and is legitimately serving up pages, the load balancer will begin redirecting requests to it. This is why we use amazon - handling stuff like this is just a matter of calling their utilities.