by Organisers @virtualddd | Mar 24, 2022
Actor model frameworks use at-most-once delivery as a default rule for their message transport, and they do it for good reasons. Efficient reliable messaging requires business-level acknowledgement, and this it not something that the actor model framework is built...
by Organisers @virtualddd | Jan 3, 2022
When we talk about implementing an event-sourced system, we hear from the experts in the subject that Event Sourcing, in essence, is an easy concept. You don't need a framework, they say. Or do you? When building a production-grade system, I personally always...
by Organisers @virtualddd | Jan 3, 2022
This is the story of how I used EventStorming to visualize, make explicit, discuss and fix the process of a non-digital company struggling with the typical mess of every other organization: unclear requirements, bad capacity management, and chaotic patterns...
by Organisers @virtualddd | Jan 3, 2022
One way or another, each system contains some kind of boundaries. I would go so far and claim that even the dreaded Big Ball of Mud systems consist of parts that could be perceived as separate though undoubtedly only under deep scrutiny. The difference is in the...
by Organisers @virtualddd | Jan 3, 2022
Have you considered using an actor model to build an event based CQRS system? Why not? Actors and DDD are a match made in heaven! There are many cool building blocks in actor frameworks like Akka.NET that make it easier to implement a CQRS system with Event Sourcing....
