Resources
Articles, papers, talks, and videos around Event Sourcing and the products built for it – from the blog and the library.
EventSourcingDB 1.3.0 is out, and it is faster and more stable than any version before it. Writing and EventQL queries are considerably faster, reading is faster as well, every request is bounded in time, and more than sixty fixes went in. Next to all that, it brings a new API that reports the outcome of every request it accepts in its body and names every error with a code of its own.
Java Client SDK 1.0 Now AvailableToday we're pleased to announce the release of the official Java Client SDK for EventSourcingDB, version 1.0. If you're building on the JVM, you can now add a single dependency to your project and write your first event from Java a few minutes later.
ArchitectureKit: DDD, CQRS, and Event Sourcing for GoLast week, we released ArchitectureKit: building blocks for applications based on Domain-Driven Design, CQRS, and Event Sourcing, in Go and on top of EventSourcingDB, open source under the MIT license. If you have been following us for a while, you may remember wolkenkit, our framework for event-sourced applications. ArchitectureKit is the first thing in that tradition we have released since.
ESDM 0.15.0: Last Call Before 1.0Ten weeks ago we put ESDM under the MIT license and asked you to tell us what works and what doesn't. ESDM 0.15.0, released last week, is what came back. It is a big release, and most of it traces to someone using ESDM on a real model and reporting what happened: a vocabulary that speaks more than one language, a command that turns a model into a browsable set of pages, a stable way to point at any element from outside the model, and a linter that explains every finding it makes.
There Is No Row to LockOptimistic locking is one of those techniques you learn once and then use everywhere. A version column, an UPDATE ... WHERE version = 7, and whoever arrives second finds zero rows affected and has to try again. It is cheap, it needs no coordination, and it has kept relational systems correct for decades.
Not an Event YetEvery event stored in EventSourcingDB is a CloudEvent. What your application sends in order to write one is not. It is missing seven of the eleven fields a stored event carries, and if you try to supply them yourself, the database rejects the whole request.
Event Sourcing and CQRS as the foundation for AI that understands the domain, with events as data products.
DWX hakt nach: Event Sourcing, CQRS & Data Mesh – Golo Roden im InterviewAn interview at the DWX on Event Sourcing, CQRS, and Data Mesh.
Sovereignty Is the Ability to LeaveReal sovereignty is the ability to leave, and that is decided in your architecture – down to the most portable form your data can take.
Alles rund um CQRS und Event-SourcingAn evening about CQRS and Event Sourcing at the .NET User Group Karlsruhe.
… und dann DELETED der Wolf die GroßmutterWhy CRUD fails at the processes of a domain, and how Event Sourcing and CQRS do better.
You Don't Even Know Your Most Important Questions YetMost systems store only the current state; Event Sourcing keeps what happened, for audits, analytics, and the questions you cannot foresee.