2 ms·
Me too. I suspect there's medium and longterm costs that probably skew my "gut feel" of how much cheaper that'd be. I wonder what the real costs associated with
by bigiain 13y ago
Me too. I suspect there's medium and longterm costs that probably skew my "gut feel" of how much cheaper that'd be. I wonder what the real costs associated with feeding a roomful of local servers replacement disks/ram/powersupplies are, and what a realistic replacement schedule for the hardware is?
Sure AWS is expensive for 24/7/365 applications, but I suspect there's some "in between ground" where Amazon's economies of scale make it less expensive to just pay them to deal with owning and maintaining the hardware (and ensuring you write your applications to be able to deal with cloud instances vanishing underneath you randomly).
- waps 13y agoIf you want a worldwide site though, AWS gets you in 10 locations around the world. This would take even an experienced admin a month for just the admin stuff to get going. An inexperienced one ... half a year ? (but it's still better to have a webserver on AWS, that simply 302s to your "real" services, or only provides a skeleton web page, though 302'ing is better, without it you'll quickly run into difficulties with same origin policy. 302 redirects will also change much faster than dns updates).