testing
How Inorderly Was Tested With Shuffled Arrivals and Killed Runs
Inorderly makes one promise above the rest: the same events give the same output, byte for byte, however they arrived. That’s an easy thing to say and an easy thing …
Version 0.1, free and open source
Same events in, same sequence out
Inorderly takes events that arrive late, twice or out of order and releases them as one sequence. Feed it the same events again, shuffled and repeated, and it writes the same output, byte for byte, with a hash to prove it.
200,000
Shuffled arrival orders of 10,000 tangled event sets, with repeats and restores; every set gave one output
30 kills
SIGKILL at random moments in one checkpointed run; the output matched an uninterrupted run byte for byte
344,000
Arriving events a second on two cores, two-thirds of them repeats, put in order
Apache 2.0
License for all of the code
Measured on a two-core Linux cloud machine with Go 1.24. The test logs are on GitHub.
Guides and notes
releases
Inorderly 0.1 Turns Late, Duplicate and Out of Order Events Into One Repeatable Sequence
Events don’t arrive the way they happened. A webhook gets retried and the same order turns up twice. A payment service’s clock runs behind the …
use cases
Making a Ledger, a Billing System and an Audit Agree on Every Balance
Two systems that read the same events should end up in the same state. They often don’t, and the reason is rarely the code. It’s the order. A withdrawal that …
use cases
Merging Two Lossy Market Data Feeds Into One Tick Stream With Exact Gaps
Exchanges send market data twice, over two lines usually called A and B. Each line drops a packet now and then, and rarely the same one. Take both, keep the first copy of …
use cases
Ordering Retried Webhooks So Payments Never Come Before Their Orders
A shop takes its events as webhooks. Checkout sends the order. Payments sends the payment, and later a refund if there is one. The warehouse sends the shipment. Three …
use cases
Ordering Sensor Telemetry From Devices With Bad Clocks and Late Uploads
Sensors are the worst-behaved producers there are. Their clocks drift. Some sit behind a gateway that forwards readings in batches. Some lose their connection for a …
event ordering
What Is Deterministic Event Ordering and Why a Replay Should Give the Same Answer
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 …
the name
Where the Name Inorderly Comes From
Inorderly is two phrases run together. “In order” is the job: events lined up one after another, the way they should be. “Orderly” is the manner: …
Questions or ideas?
If Inorderly nearly fits your pipeline, or you'd like it to do something it doesn't yet, write in.