GoKawiilEventSourcingDB 1.3.0 ships with new v2 API and performance gains
EventSourcingDB has released version 1.3.0, which speeds up writes, EventQL queries and reads, adds time bounds on every request, and includes more than sixty bug fixes. The release introduces a new v2 API that runs alongside the existing v1 API on the same data, reporting every request's outcome in its response body with linked error codes, and adding recursive precondition checks. The v1 API remains supported until January 31, 2027, and documentation has moved to eventfoundation.io.
GoKawiil's interpretation of the reporting above, not reported fact.
Running v2 alongside v1 lets developers migrate at their own pace rather than facing a forced cutover, which could reduce upgrade risk for existing deployments. The shift to embedding outcomes and detailed error codes directly in response bodies suggests an effort to make client error-handling more predictable than relying on HTTP status codes alone. Recursive preconditions could simplify logic for applications that need to make decisions based on entire branches of data rather than single records.
- EventSourcingDB 1.3.0 improves write, query and read performance and fixes over sixty issues.
- A new v2 API reports request outcomes and linked error codes in the response body, running in parallel with v1 until January 31, 2027.
- Recursive preconditions and streamed responses with explicit end markers and heartbeats are new in this release, and documentation has moved to eventfoundation.io.
Source: eventfoundation.io, 2026-11-11
Published there as: “EventSourcingDB 1.3.0 Is Available”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.