←back to thread

59 points hui-zheng | 1 comments | | HN request time: 0.213s | source
Show context
kayodelycaon ◴[] No.40214769[source]
Crash-only is really hard to implement if another system is involved that isn't crash-only. If you crash in the middle of a network request, you may not know what state the other system is in.

I've had to deal with buggy mainframe software whose error messages had no relation to how much an operation succeeded. (And no way to ask it after the fact...) Welcome to the special hell.

replies(4): >>40215739 #>>40218514 #>>40219895 #>>40220818 #
1. WhyNotHugo ◴[] No.40220818[source]
Regular software can crash in the middle of a network request too (e.g.: someone accidentally unplugged the wrong network cable, power outage, etc).

Crash-only software is likely to test recovery of such situation.