https://inorderly.com/tags/determinism/ Recent content in Determinism on Inorderly.com Hugo en-us Sun, 18 Oct 2026 00:00:00 +0000 https://inorderly.com/how-inorderly-was-tested-with-shuffled-arrivals-and-killed-runs/ Sun, 18 Oct 2026 00:00:00 +0000 https://inorderly.com/how-inorderly-was-tested-with-shuffled-arrivals-and-killed-runs/ <p>Inorderly makes one promise above the rest: the same events give the same output, byte for byte, however they arrived. That&rsquo;s an easy thing to say and an easy thing to get slightly wrong, so most of the tests do nothing but try to break it. They shuffle events, repeat them, cut the stream with snapshots, and kill the process in the middle of a run.</p> <p>Every result below comes from the files in <a href="https://github.com/inorderly/inorderly/tree/main/test/results">test/results</a>, recorded from version 0.1.1 on a two-core 2.1 GHz Xeon cloud machine running Linux, with Go 1.24. The same tests run on every push, on Linux, macOS and Windows.</p> https://inorderly.com/what-is-deterministic-event-ordering-and-why-a-replay-should-give-the-same-answer/ Sun, 18 Oct 2026 00:00:00 +0000 https://inorderly.com/what-is-deterministic-event-ordering-and-why-a-replay-should-give-the-same-answer/ <p>Deterministic event ordering means that the same set of events always comes out in the same sequence, no matter the order they arrived in or how many times each one arrived. Feed the events in once and you get a sequence. Feed them in again next week, shuffled, with half of them sent twice, and you get the same sequence, byte for byte.</p> <p>That sounds like it should be the default. It almost never is. Most systems process events in arrival order, and arrival order is an accident of networks, retries and clocks.</p>