tsoracle makes uncertain sequence allocation an explicit error
tsoracle is a Rust service for issuing increasing timestamps and contiguous sequences across machines. Its leader persists and replicates an allocation before returning IDs. Sequence requests expose an uncertain result when a failure leaves the client unable to tell whether allocation succeeded, rather than silently retrying a request that could consume another range of numbers.
tsoracle
Why it matters
An ordered ID service and a gapless business record are different promises, especially when a client loses the response.
More context
Undated project discovery. The documented local trial uses cargo install tsoracle, then tsoracle, with file persistence and a loopback gRPC listener. Distributed drivers include OpenRaft and OmniPaxos. Test failover and the SeqUncertain handling path, not only successful allocations.
Keep in mind
Project guarantees were read, not independently tested. Allocating a contiguous block does not ensure an application uses every number or commits its business transaction; callers must handle ambiguity and consumption themselves.
Original read