EventSourcingDB 1.3 makes stream completion explicit
EventSourcingDB 1.3 introduces a second API that reports accepted requests’ outcomes in their response bodies. Finite event streams end with an explicit completion item, helping clients distinguish success from a dropped connection; waiting streams send heartbeats. The release also bounds requests and idle connections, but upgrading requires backups because older versions cannot reopen the updated data directory.
Event Foundation · Nov 11, 2026
Why it matters
Explicit completion signals prevent a partial network response from looking like a complete event history.
More context
Update client SDKs first, stop the old server before starting 1.3, and test proxies for the QUERY method. SDKs support both APIs; v1 support runs through January 31, 2027. Try a backup-and-restore rehearsal before upgrading production.
Keep in mind
Released database update with incompatible storage and query behavior changes. Docker’s user ID changes, and initial index rebuilding temporarily blocks some operations; deployment costs and licensing were not assessed.
Original read