You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ordered dispatch through leased lanes (design §6.4).
Scope
Hash the UTF-8 ordering key into N lanes (the existing EF writer uses FNV-1a).
Lease lanes through the leases table with database-clock membership heartbeats and fair rebalancing as instances join and leave.
Lane owners read pending rows in ID order with the partial (lane, id) index. Do not overtake scheduled or live-claimed heads; parked keys must not block other keys.
Drain connected send transactions before ownership transfers and preserve native message identity and ordering semantics.
Acceptance criteria
Real PostgreSQL tests cover competing connected owners, membership joins/leaves, expiry, connection termination during native send, replay and ascending visible ID order across recovery.
The website documents registration, immutable named options, shutdown and the at-least-once failure boundary.
Ordering boundary: Order describes committed rows visible to a scan in UUID order, not commit order between concurrent writers. Database fencing cannot retract a native request already accepted by the broker; a crash can replay an identity, and an in-flight request after database connection loss can arrive late. The implementation must document this limitation rather than claim broker-side fencing or exactly-once delivery. D34 records this protocol explicitly.
Triage against origin/main bf3191f: this issue's implementation remains outstanding; the outbox packages still contain options only. Added native blocked-by dependencies on #29, matching the prerequisites already documented in the issue. Existing scope and acceptance criteria remain current.
Activity
thomhurst commentedon Nov 1, 2026
Triage against origin/main bf3191f: this issue's implementation remains outstanding; the outbox packages still contain options only. Added native blocked-by dependencies on #29, matching the prerequisites already documented in the issue. Existing scope and acceptance criteria remain current.
fix: commit ordered dispatch progress within batch deadline (#32)
fix: drain ordered outbox backlog without polling delays (#32)
feat: dispatch ordered outbox messages through leased lanes (#32)
fix: commit ordered dispatch progress within batch deadline (#32)
fix: drain ordered outbox backlog without polling delays (#32)
fix: commit ordered dispatch progress on preparation failure (#32)
feat: dispatch ordered outbox messages through leased lanes (#32)
9 remaining items
fix: commit ordered dispatch progress on preparation failure (#32)
fix: preserve dispatch configuration parsers after rebase (#32)
fix(docs): align outbox dispatch status and replay limits (#32)
perf: reduce ordered dispatch database churn (#32)
fix: compile regression harness without ordered dispatch probes (#32)
feat: dispatch ordered outbox messages through leased lanes (#32)
fix: commit ordered dispatch progress within batch deadline (#32)
fix: drain ordered outbox backlog without polling delays (#32)
fix: commit ordered dispatch progress on preparation failure (#32)
fix: preserve dispatch configuration parsers after rebase (#32)
fix(docs): align outbox dispatch status and replay limits (#32)
perf: reduce ordered dispatch database churn (#32)
Dispatch ordered PostgreSQL outbox messages through leased lanes (#140)