How much of an event store could move to S3? I measured it for skilj: 16% with ~100 B events, ~60% from 1 KB up. The tag index has to stay in Postgres. Nothing is built yet, so input is very welcome: codeberg.org/gklijs/SkilJ... #EventSourcing #Rust

How much of an event store could move to S3? I measured it for skilj: 16% with ~100 B events, ~60% from 1 KB up. The tag index has to stay in Postgres. Nothing is built yet, so input is very welcome: codeberg.org/gklijs/SkilJ... #EventSourcing #Rust
Finally, lots of code: in this post in my event-sourcing series, we take a close look at the ValueProjector code used to project events.
Surprisingly simple! π
In the latest post in my series on event sourcing, we look at what we can do with bi-temporal events projected onto a timeline. For example, while we are typically interested in the latest state in normal event sourcing, in bi-temporal event sourcing ...
I'll be running a "beta test" soon and then will open it up to the public in January. I'll limit attendance at 4-6 people to give everyone proper attention and be able to ensemble on the codebase.
I'm running a remote "alpha test" of my #EventSourcing workshop and I think it's going well?? Great questions and hopefully participants are getting a deeper understanding and building a mental model of how Event Sourcing works. Day 2 is done and we have yet to look at code!
After a long summer break, I'm continuing my blog post series on event sourcing, focusing on how to handle acceptance workflows: an employee makes a change that needs approval from, e.g. their manager. So we need to accept or reject events.
Insight: CQRS doesn't need event sourcing, and event sourcing doesn't need CQRS. Paring them often leads to unnecessary complexity. Consider a CRM system where only transactional data needs CQRS, leaving event sourcing for logs. Complexity avoided, data integrity improved. #CQRS #EventSourcing
Apache Maka (Incubating) records every model message, tool call and permission decision as an append-only event, with its UI, next prompt and crash recovery presented as projections of that log: https://github.com/apache/maka
#AIAgents #EventSourcing #TypeScript
Curious about event sourcing but not sure where to start? π
Build a feature from the events up in this hands-on workshop with @ted.dev at #dev2next and see how event sourcing works in practice.
π www.dev2next.com/schedule
ποΈ Get tickets: dev2next.com
π
October 12-15
Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!
Details: euregjug.dev/#events
Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! www.meetup.com/microservic...