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 …
Tag
Event Ordering
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 …