Timeline for CQRS-Event Sourcing: how to process events in the expected order inside the read model
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2018 at 22:28 | history | edited | Christophe | edited tags | |
| Aug 24, 2018 at 15:01 | history | tweeted | twitter.com/StackSoftEng/status/1033006341017808897 | ||
| Jul 11, 2018 at 22:52 | vote | accept | Enrico Massone | ||
| Jul 11, 2018 at 22:38 | comment | added | Constantin Galbenu | yes, so they all receive the events but they ignore the events outside the range. So, the problem is not the order, like in your title, but the owning of streams. | |
| Jul 11, 2018 at 20:44 | comment | added | Enrico Massone | @ConstantinGalbenu so basically the idea is that the two instances of my read model app could process only the events of two non overlapped ranges of aggregate ids. This way, they can work concurrently without breaking the consistency of the read model. Each of them could be woken up by a message published to the service bus and can decide what to do, by examining the Id of the aggregate from which the event was originated (no more competing consumers, now all the instances have a chance to get the message and examine it). Did you a mean a solution like this ? | |
| Jul 11, 2018 at 13:53 | answer | added | VoiceOfUnreason | timeline score: 9 | |
| Jul 11, 2018 at 13:08 | comment | added | Constantin Galbenu | see stackoverflow.com/questions/49891905/… | |
| Jul 11, 2018 at 12:58 | review | First posts | |||
| Jul 11, 2018 at 17:11 | |||||
| Jul 11, 2018 at 12:55 | history | asked | Enrico Massone | CC BY-SA 4.0 |