4 ms·
To me the ease of use is key. I don't want to deal with outages, hardware failures, networking issues, etc. I only want to focus on the software. That's why I d
by edem 5y ago
To me the ease of use is key. I don't want to deal with outages, hardware failures, networking issues, etc. I only want to focus on the software. That's why I don't understand why would anybody (apart from some special cases) would run their own servers.
- darkwater 5y agoYou will still have to deal with outages (even if probably at a much lower rate). Just today I got a confirmation from AWS that the 1h outage that our production, multi-AZ RDS database suffered *three months ago* was due to an underlying failure in their storage subsystem. I didn't have to fix any SAN or fiber issue, true, but I lost hours puzzling and debugging things to understand why it failed, with no good answer (until today).
- edem 5y agoLet's be honest. It is much different than having to sit in the car in the middle of the night to change a hard drive in the server that just failed because of a power surge.
- darkwater 5y agoGonna go the typical HN nitpicking on examples > It is much different than having to sit in the car in the middle of the night to change a hard drive in the server that just failed because of a power surge. Never ever had to go at night in a data center to replace a single disk failure, even in my DC days. Always the 1st working day after the disk failure, since they were redundant. Now, network gear upgrades during the nights, those I made a few and I'm happy they are history for me now. But even in a cloud world you have to do from time to time low-traffic time interventions.