Which events to store with event-sourcing?
I’m planning out the events that my application will be creating, but am running into problems with my design. I believe I’m not applying the event-sourcing concepts correctly.
How to handle duplicate events when replaying event store?
If two aggregates are listening to the same event; then the event will be stored in an event store twice, once for each aggregate.
How to handle duplicate events when replaying event store?
If two aggregates are listening to the same event; then the event will be stored in an event store twice, once for each aggregate.
How to handle duplicate events when replaying event store?
If two aggregates are listening to the same event; then the event will be stored in an event store twice, once for each aggregate.
Is Event sourcing a good fit for database sync (master-multiple-slaves)?
I’m looking for a good way to maintain in sync local sqlite databases that could be offline to a master one, for a invoice app.
CQRS – How can a command properly validate when queries are required?
I’m aware that this question has been asked several times, but I have some concerns regarding querying from the write side that I don’t see addressed in the already existing questions, more especifically regarding eventual consistency in the command model.
In CQRS/ES, can a command create another command?
In CQRS/ES, a command is sent from the client to the server and routed to the appropriate command handler. That command handler loads an aggregate from its repository, and calls some method on it, and saves it back to the repository. Events are generated. An event handler/saga/process manager can listen to these events in order to issue commands.
What is the difference between Event Driven and Event sourcing?
I’m studying domain driven design (DDD) and came across terms: Event Driven and Event sourcing. I know it’s about publishing event from producer to consumer, and store the log, so my question is:
Is one to one mapping necessary between Write Applications and Read Applications
Introduction: We have a bunch of micro services (about 40) to serve our customers.