https://flowchassis.com/tags/crash-recovery/ Recent content in Crash Recovery on FlowChassis.com Hugo en-us Sun, 18 Oct 2026 00:00:00 +0000 https://flowchassis.com/how-flowchassis-was-tested-with-240-worker-kills-and-not-one-lost-order/ Sun, 18 Oct 2026 00:00:00 +0000 https://flowchassis.com/how-flowchassis-was-tested-with-240-worker-kills-and-not-one-lost-order/ <p>FlowChassis makes one main promise: whatever happens to the process, every run picks up where it stopped, and nothing it did is lost or done twice without warning. The only honest way to test that promise is to break the process, over and over, at moments nobody chose, and then check the results against something the engine can&rsquo;t fake.</p> <p>So that&rsquo;s what the tests do. This post goes through them, with the numbers from the recorded results in the <a href="https://github.com/flowchassis/flowchassis/tree/main/test/results">code repository</a>. Every figure below comes from those files.</p> https://flowchassis.com/video-transcoding-with-flowchassis-survives-a-crash-without-starting-over/ Sun, 18 Oct 2026 00:00:00 +0000 https://flowchassis.com/video-transcoding-with-flowchassis-survives-a-crash-without-starting-over/ <p>Some jobs take minutes or hours. Transcoding a long video is the classic one. The usual design is a worker that picks up the job and grinds through it, and when that worker dies at 80 percent, say because a deploy restarted it, the job starts again from zero.</p> <p>Starting over is fine once. On a busy system with regular deploys it means the longest jobs are the ones that never finish.</p>