Configure the object and Stream
Implement the consistency boundary
A Verglas Stream binding inside a Durable Object uses the host’s transactional
storage.stream-send path, not an external HTTP request. The accepted-row
mutation and publication are released through the same object event boundary;
a failed publication does not silently mark the ID delivered. Preserve the
event ID downstream as an additional idempotency key.Retention choices
An indefinitely growing deduplication set is rarely necessary. Choose a policy that matches the source’s retry window:- Keep IDs forever when they represent immutable business transactions.
- Store an expiration timestamp and use an alarm to delete old IDs when the source guarantees a bounded retry period.
- Hash a tenant and time bucket into the object name when one ID per object is too fine-grained for your workload.
