causal-order is a deployable event-ordering runtime for distributed systems
that need bounded replay handling, reconnect-heavy stream reconciliation, explicit
late-arrival policy, and operator-visible output rather than timestamp-only ordering.
npm install causal-order
View package
orderEvents() for bounded replay, recovery, and audit workloadsorderEventStream() for continuous, delayed, and reconnect-heavy flowsStart with fit, not implementation. Use the quick-start, supported-usage boundary, and real examples before you wire a runtime into a system that has to keep running under replay, recovery, and stream pressure.
Once the fit is clear, move into package surface, policy, and runnable entrypoints that map onto actual replay pipelines, recovery jobs, and long-lived stream handling.
Inspection and operator views support that runtime posture by making deployed ordering explainable, reviewable, and honest under real backlog, reconnect, and anomaly pressure.
Replayed events can look newer than originals. Offline devices sync late. Ingestion order can
differ from creation order. causal-order is built for systems that still need a
deployable ordering runtime without turning those realities into false certainty.
causal-order is the core event-ordering runtime in the package ecosystem.
Companion packages such as
@causal-order/dedupe
can add focused workflow capabilities like duplicate-event filtering before causal ordering
without turning the core runtime into an all-in-one platform.
Deployment guides, policy choices, replay workflows, and operator follow-through for the current runtime surface.
Mental models, terminology, and deeper explanations for concurrency, uncertainty, and honest ordering claims.
The runtime entrypoints, inspection helpers, and exported types you build against in bounded and streaming deployments.