6 ms·
I fail to see how this supports your claim that you can get by with "a few minutes per month" of devops. In fact, it's a classic red herring. Your original cla
by empthought 6y ago
I fail to see how this supports your claim that you can get by with "a few minutes per month" of devops. In fact, it's a classic red herring.
Your original claim is quite unrealistic and you'd do well to retract it. It's bad advice both for public cloud and for self-managed efforts alike.
- daniellarusso 6y agoWhen I used to work for an MSP, we would sell Dell servers to rural banking groups. We supported disaster recovery and high availability deployments. Any failed component, Dell would send us a replacement in less than 24 hours.
- deleted 6y ago[deleted]
- AnIdiotOnTheNet 6y ago24? I guess it's that long because it is rural? We use Dell servers and I sleep a bit better having seen their 4hr support replace a motherboard with a bad lifecycle controller within 2 hours of the initial call. Try calling Amazon and getting that kind of response for your problems.
- daniellarusso 6y agoYeah, my closest Target store and major airport is over 2 hours away. But, yeah, that is worse-case scenario.
- kortilla 6y agoBut it is a few minutes per month. A properly architected application won’t depend on a single server so a hardware failure will be as unimportant as it is the serverless world.
- empthought 6y agoArchitecting a system properly is one of the key functions of devops. You don’t get it by investing a few minutes per month, whether public cloud or bare metal.