Thanks for your reply! I "feel" there is similarity, resonance... but still I cannot really grasp it. Can you try to make your description "less meta"? 😉 The examples in my post are about what to record inside a software to track state changes. Your examples seem to be about the development process of software and you're calling it "genealogical development". I am a little confused (but I like the allusion to quantum mechanics).
Also, I'm trying to think how to migrate data from my 10-year old CRUD application (many dozens of entities and RDBMS tables) into an AQ system. Maybe simple "entity migrated" events to start with.
I do appreciate your ideas. Previously, ES and CQRS and bounded contexts and aggregates and what not were hard for my team to grasp. This approach is very straight-forward. The necessary projections for queries and reports seem obvious.
This was a great read. Inspiring and hit close to home. I felt like I needed to respond immediately because it resonates so deeply with the course we're on. https://thetimethatremains.substack.com/p/events-in-superposition
Thanks for your reply! I "feel" there is similarity, resonance... but still I cannot really grasp it. Can you try to make your description "less meta"? 😉 The examples in my post are about what to record inside a software to track state changes. Your examples seem to be about the development process of software and you're calling it "genealogical development". I am a little confused (but I like the allusion to quantum mechanics).
Ralf, these are very interesting articles and much appreciated.
Do you know of a reference architecture, or an example system built along these lines? Or should we all be trying to write one?
Also, do you feel like a purpose-built graph database would be a more effective or performant event store, compared to a traditional RDBMS?
Thanks,
Dave
Glad you like the article!
There are no examples yet for Story Recording. But Rico and I are working on them. Subscribe to this substack and you'll be informed... 😉
If a graph database or some purpose built database or an RDBMS is the best choice we'll see. It probably depends on several aspects.
For now I am concerned with a convincing concept. If the concept holds then efficient implementations will be found. It happened with RDBMS, too.
Also, I'm trying to think how to migrate data from my 10-year old CRUD application (many dozens of entities and RDBMS tables) into an AQ system. Maybe simple "entity migrated" events to start with.
I do appreciate your ideas. Previously, ES and CQRS and bounded contexts and aggregates and what not were hard for my team to grasp. This approach is very straight-forward. The necessary projections for queries and reports seem obvious.
This is not a small project. Please send me a DM on LinkedIn and we'll find a way to talk about this.