3 ms·
My experience is that the labor involved in maintaining an AWS setup is typically far higher than the labor involved in maintaining a system on leased hardware
by vidarh 11y ago
My experience is that the labor involved in maintaining an AWS setup is typically far higher than the labor involved in maintaining a system on leased hardware or managed hosting, because you still need to deal with the fallout of most types of failures, but without insight into what's going on below the hood or ability to set up a system geared specifically towards your workload.
- noir_lord 11y agoMine as well but this is contingent on having people on hand who can open the hood and troubleshoot, if not and you are weak on the OPS side or earning so much per customer that hosting is a secondary consideration then I can see the value in AWS, it's just not my default choice. Also frankly I loathe dealing with AWS's web interfaces for anything - frankly they are embarrassingly bad for a company that prides itself on end user experience.
- vidarh 11y agoIf you don't have people on hand who can "open the hood and troubleshoot" I'd argue you don't have people that can run a service on AWS reliably. The number of gotchas I've run into with AWS is far higher than what I've had to deal with with managed hosting or even bare metal hardware. (I'm assuming you're talking metaphorically, as for my part we use onsite repair warranties to deal with failure of new hardware, and just replace old hardware except when it's something very obvious like a failed drive - it's rarely worth the trouble to do a lot of diagnostics at smaller scales; in any case you can still save and avoid this by using a managed hosting provider)
- noir_lord 11y agoIndeed, I've run owned bare metal but these days I rent them if I need them but largely VPS's suffice, also feel a lot more confident if something I set up develops a problem since its what you don't know that bites you at 3am.