3 ms·
> Reducing the number of points of failure is almost always a good idea. Reducing the single points of failure is usually a good idea. You can easily reduce t
by marcosdumay 5y ago
> Reducing the number of points of failure is almost always a good idea.
Reducing the single points of failure is usually a good idea.
You can easily reduce the number of points of failure by reducing redundancy and removing sanity checks from your process. Doing that does normally not improve your reliability.
Sending the logs to your SAN for it to write in a couple of disks arrays is much more reliable than writing to stderr (stdout is not a reasonable place to log failures) and redirecting it to your local disk.
- marginalia_nu 5y agoReducing points of failure in general is a good idea too. Single points of failure are especially bad, but most major errors are the confluence of multiple things going wrong that while alone would be bad, but together make for an absolute disaster.
- marcosdumay 5y agoReducing points of failure in general is an iffy idea that can be good or bad depending on how you do it. A lot of complexity is there for good reason, a lot for bad reason, and some for no reason at all. It takes a very nuanced and specific work to determine what is what, and talking in generalities about it is a very bad idea on itself.