3 ms·
I have a service at work that only needs to be up during a couple of 4 hour intervals every week. It's one of the least stressful elements of my job. There's a
by hinkley 5y ago
I have a service at work that only needs to be up during a couple of 4 hour intervals every week. It's one of the least stressful elements of my job.
There's a cost to always-on systems, and I don't think we're accounting those costs properly (externalities). It's likely that in many cases the benefits do not outweigh the costs.
I think it comes down to your ability to route around a problem. If the budgeting or ordering system is down, there are any number of other tasks most of your people can be doing. They can make a note, and stay productive for hours or days.
If you put all of your software on one server or one provider, and that goes down, then your people are pretty much locked out of everything. Partial availability needs to be prioritized over total availability, because of the Precautionary Principle. The cost of everything being down is orders of magnitude higher than the cost of having some things down.