Category "event-sourcing"

Event Sourcing - Replaying Events

Imagine an event sourced system where there exists a consuming service that is subscribed to a certain Event A. Once this consumer detects Event A has been emit

Event Storming | Command | Validation | Rules | Make it visible

I'm practicing event-storming, with sticky notes and stuffs. But one thing is missing: command validation (rules to be satisfied for a command to be accepted /

Using Kafka as a (CQRS) Eventstore. Good idea?

Although I've come across Kafka before, I just recently realized Kafka may perhaps be used as (the basis of) a CQRS, eventstore. One of the main points that Ka