📦 gember/event-sourcing 0.21.1
Use case driven EventSourcing - Let go of the Aggregate with the Dynamic Consistency Boundary (DCB) pattern.
🔗 https://github.com/GemberPHP/event-sourcing
Use case driven EventSourcing - Let go of the Aggregate with the Dynamic Consistency Boundary (DCB) pattern.
🔗 https://github.com/GemberPHP/event-sourcing
November 1, 2026 at 6:14 PM
📦 gember/event-sourcing 0.21.1
Use case driven EventSourcing - Let go of the Aggregate with the Dynamic Consistency Boundary (DCB) pattern.
🔗 https://github.com/GemberPHP/event-sourcing
Use case driven EventSourcing - Let go of the Aggregate with the Dynamic Consistency Boundary (DCB) pattern.
🔗 https://github.com/GemberPHP/event-sourcing
Sunday hack: now that my Ruby Eventsourcing library has an API for statecharts (nested state machines), I reused it to model the lifecycle of consumer groups running in the background, including failures and retries.
October 25, 2026 at 5:12 PM
Sunday hack: now that my Ruby Eventsourcing library has an API for statecharts (nested state machines), I reused it to model the lifecycle of consumer groups running in the background, including failures and retries.
This week in Eventsourcing: I started exploring a kind of little algebra for declarative event queries. You can express arbitrary "states" made up of sequences of events with ordering assertions.
October 27, 2026 at 1:51 PM
This week in Eventsourcing: I started exploring a kind of little algebra for declarative event queries. You can express arbitrary "states" made up of sequences of events with ordering assertions.
I'm coming at CQRS from the Eventsourcing angle, which may or may not map to the same idea of "slices". I have PLENTY of opinions on my website, if you have time to kill ismaelcelis.com
Ismael Celis
Ramblings about code
ismaelcelis.com
October 24, 2026 at 4:55 PM
I'm coming at CQRS from the Eventsourcing angle, which may or may not map to the same idea of "slices". I have PLENTY of opinions on my website, if you have time to kill ismaelcelis.com
skilj 0.1.1 is out
Event sourcing in Rust on one Postgres database, without aggregates: each command is checked against exactly the events it shares tags with.
GraphQL + REST generated from your types, forgettable personal data.
github.com/gklijs/SkilJ
#rustlang #EventSourcing
Event sourcing in Rust on one Postgres database, without aggregates: each command is checked against exactly the events it shares tags with.
GraphQL + REST generated from your types, forgettable personal data.
github.com/gklijs/SkilJ
#rustlang #EventSourcing
GitHub - gklijs/SkilJ: Event sourcing with Dynamic Consistency Boundaries on Postgres, with GraphQL and REST generated from your types
Event sourcing with Dynamic Consistency Boundaries on Postgres, with GraphQL and REST generated from your types - gklijs/SkilJ
github.com
October 23, 2026 at 8:12 AM
skilj 0.1.1 is out
Event sourcing in Rust on one Postgres database, without aggregates: each command is checked against exactly the events it shares tags with.
GraphQL + REST generated from your types, forgettable personal data.
github.com/gklijs/SkilJ
#rustlang #EventSourcing
Event sourcing in Rust on one Postgres database, without aggregates: each command is checked against exactly the events it shares tags with.
GraphQL + REST generated from your types, forgettable personal data.
github.com/gklijs/SkilJ
#rustlang #EventSourcing
Today's post in my event sourcing series is a short one showing how fast the value projector is that projects events into a single value representing the current state:
www.planetgeek.ch/2026/10/20/e...
#EventSourcing #fsharp #dotnet
www.planetgeek.ch/2026/10/20/e...
#EventSourcing #fsharp #dotnet
Event Sourcing: Is our Projection Code fast enough?
In this part of my event sourcing series, we take a quick, pun intended, look at how fast the projector we saw in the last post actually runs. The projector gets a list of events as input and…
www.planetgeek.ch
October 20, 2026 at 8:20 AM
Today's post in my event sourcing series is a short one showing how fast the value projector is that projects events into a single value representing the current state:
www.planetgeek.ch/2026/10/20/e...
#EventSourcing #fsharp #dotnet
www.planetgeek.ch/2026/10/20/e...
#EventSourcing #fsharp #dotnet
Die Auftragsliste in Cosmos DB kann dem Event Store hinterherlaufen. Idempotente Projections und Stream-Versionen halten Updates geordnet. lunaris.digital/blog/article... #AzureCosmosDB #EventSourcing
October 20, 2026 at 10:45 AM
Die Auftragsliste in Cosmos DB kann dem Event Store hinterherlaufen. Idempotente Projections und Stream-Versionen halten Updates geordnet. lunaris.digital/blog/article... #AzureCosmosDB #EventSourcing
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
[Discussion] Tiered storage: moving old event payloads to object storage (S3)
> **Status: under discussion.** Nothing here is planned or built yet. This issue collects the investigation so far and asks for input. If you'd use this, if you already run into storage costs with an ...
codeberg.org
October 14, 2026 at 9:07 AM
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! 😂
www.planetgeek.ch/2026/10/12/e...
#EventSourcing #dotnet #fsharp
Surprisingly simple! 😂
www.planetgeek.ch/2026/10/12/e...
#EventSourcing #dotnet #fsharp
Event Sourcing: A close look at the projector for values
In this part of my event sourcing series, we look at implementing the projector for values (uni-temporal events / normal event sourcing). You'll see the full source code for our ValueProjector, which…
www.planetgeek.ch
October 13, 2026 at 8:20 AM
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! 😂
www.planetgeek.ch/2026/10/12/e...
#EventSourcing #dotnet #fsharp
Surprisingly simple! 😂
www.planetgeek.ch/2026/10/12/e...
#EventSourcing #dotnet #fsharp
3 SEATS UNTIL SELLOUT
You can still join my workshop that starts Monday. There will never be a lower price, and I'm told my next event has a pricing increase.
👇 Registration below.
kalele.io/iddd-workshop
You can still join my workshop that starts Monday. There will never be a lower price, and I'm told my next event has a pricing increase.
👇 Registration below.
kalele.io/iddd-workshop
October 10, 2026 at 5:27 AM
3 SEATS UNTIL SELLOUT
You can still join my workshop that starts Monday. There will never be a lower price, and I'm told my next event has a pricing increase.
👇 Registration below.
kalele.io/iddd-workshop
You can still join my workshop that starts Monday. There will never be a lower price, and I'm told my next event has a pricing increase.
👇 Registration below.
kalele.io/iddd-workshop
I provide 16 heuristics for identifying Subdomains and Bounded Contexts. Even so, you still have to think 🙂
Workshop: Implementing Domain-Driven Design
4 days: $400 (save $1,600)
Dates: 12-15 October
Just a taste 👇 Registration below.
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design
4 days: $400 (save $1,600)
Dates: 12-15 October
Just a taste 👇 Registration below.
kalele.io/iddd-workshop
October 8, 2026 at 10:03 PM
I provide 16 heuristics for identifying Subdomains and Bounded Contexts. Even so, you still have to think 🙂
Workshop: Implementing Domain-Driven Design
4 days: $400 (save $1,600)
Dates: 12-15 October
Just a taste 👇 Registration below.
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design
4 days: $400 (save $1,600)
Dates: 12-15 October
Just a taste 👇 Registration below.
kalele.io/iddd-workshop
Don't be fooled by cookie-cutter solutions
- DDD is not an architecture, or architecture style
- Archetypical models are based on known solutions
- See Cynefin Framework:
Clear and Complicated: Known archetypes; ordinary is enough
Complex: Unknown unknowns; requires differentiating innovation
- DDD is not an architecture, or architecture style
- Archetypical models are based on known solutions
- See Cynefin Framework:
Clear and Complicated: Known archetypes; ordinary is enough
Complex: Unknown unknowns; requires differentiating innovation
October 8, 2026 at 10:03 PM
Don't be fooled by cookie-cutter solutions
- DDD is not an architecture, or architecture style
- Archetypical models are based on known solutions
- See Cynefin Framework:
Clear and Complicated: Known archetypes; ordinary is enough
Complex: Unknown unknowns; requires differentiating innovation
- DDD is not an architecture, or architecture style
- Archetypical models are based on known solutions
- See Cynefin Framework:
Clear and Complicated: Known archetypes; ordinary is enough
Complex: Unknown unknowns; requires differentiating innovation
October 7, 2026 at 6:55 PM
Your Domain-Driven Design workflow redefined. Learn how:
Workshop: Implementing Domain-Driven Design (nearly sold out)
4 days: $400
Dates: 12-15 October
- DDD Strategic and Tactical Design
- EventStorming
- P&A / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design (nearly sold out)
4 days: $400
Dates: 12-15 October
- DDD Strategic and Tactical Design
- EventStorming
- P&A / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
October 7, 2026 at 6:55 PM
Your Domain-Driven Design workflow redefined. Learn how:
Workshop: Implementing Domain-Driven Design (nearly sold out)
4 days: $400
Dates: 12-15 October
- DDD Strategic and Tactical Design
- EventStorming
- P&A / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design (nearly sold out)
4 days: $400
Dates: 12-15 October
- DDD Strategic and Tactical Design
- EventStorming
- P&A / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
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 ...
#EventSourcing #dotnet #fsharp
#EventSourcing #dotnet #fsharp
Event Sourcing: fun with bi-temporal timelines
In earlier parts of this series on event sourcing, we have seen that we can project bi-temporal events (events with two timestamps: when the system knew about the event and when the event takes…
www.planetgeek.ch
October 6, 2026 at 9:35 AM
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 ...
#EventSourcing #dotnet #fsharp
#EventSourcing #dotnet #fsharp
i wish i felt like it had the same immediate graspability as jsonl. i can't find ways to really disagree but i still really don't want to!
the one core difference is streaming/eventsourcing i guess? i have strong interest in ltx etc but getting architecture astronaut-ish.
github.com/superfly/ltx
the one core difference is streaming/eventsourcing i guess? i have strong interest in ltx etc but getting architecture astronaut-ish.
github.com/superfly/ltx
GitHub - superfly/ltx: Go library for the LTX file format
Go library for the LTX file format. Contribute to superfly/ltx development by creating an account on GitHub.
github.com
October 5, 2026 at 10:29 PM
i wish i felt like it had the same immediate graspability as jsonl. i can't find ways to really disagree but i still really don't want to!
the one core difference is streaming/eventsourcing i guess? i have strong interest in ltx etc but getting architecture astronaut-ish.
github.com/superfly/ltx
the one core difference is streaming/eventsourcing i guess? i have strong interest in ltx etc but getting architecture astronaut-ish.
github.com/superfly/ltx
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.
#EventSourcing
#EventSourcing
October 4, 2026 at 5:54 PM
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.
#EventSourcing
#EventSourcing
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!
October 1, 2026 at 6:21 PM
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.
www.planetgeek.ch/2026/09/28/e...
#EventSourcing #fsharp
www.planetgeek.ch/2026/09/28/e...
#EventSourcing #fsharp
Event Sourcing: two ways to enable accept/reject workflows
When an employee corrects the time they started or stopped working in a time-tracking system, a workflow typically notifies their manager or HR that the data has changed. Then, the manager or HR…
www.planetgeek.ch
September 29, 2026 at 8:20 AM
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.
www.planetgeek.ch/2026/09/28/e...
#EventSourcing #fsharp
www.planetgeek.ch/2026/09/28/e...
#EventSourcing #fsharp
September 27, 2026 at 3:27 PM
Problem fitting a hexagonal peg into a round hole?
Workshop: Implementing Domain-Driven Design
4 days: $400
12-15 October
- DDD Strategic and Tactical Design
- EventStorming, Impact Mapping
- Ports & Adapters / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design
4 days: $400
12-15 October
- DDD Strategic and Tactical Design
- EventStorming, Impact Mapping
- Ports & Adapters / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
September 25, 2026 at 5:53 AM
Problem fitting a hexagonal peg into a round hole?
Workshop: Implementing Domain-Driven Design
4 days: $400
12-15 October
- DDD Strategic and Tactical Design
- EventStorming, Impact Mapping
- Ports & Adapters / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
Workshop: Implementing Domain-Driven Design
4 days: $400
12-15 October
- DDD Strategic and Tactical Design
- EventStorming, Impact Mapping
- Ports & Adapters / Hexagonal Architecture
- Event-Driven Architecture
kalele.io/iddd-workshop
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
September 15, 2026 at 9:00 PM
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
#AIAgents #EventSourcing #TypeScript
September 13, 2026 at 4:45 PM
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
#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
#EventSourcing #Java
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
#EventSourcing #Java
September 9, 2026 at 4:03 PM
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
#EventSourcing #Java
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
#EventSourcing #Java
Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!
Details: euregjug.dev/#events
Details: euregjug.dev/#events
September 8, 2026 at 12:12 PM
Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!
Details: euregjug.dev/#events
Details: euregjug.dev/#events