randolorian

4 ms·

1. 1.▲
   by randolorian 5y ago

   > Thinking that event sourcing and CQRS are synonyms is a fundamental misunderstanding also. Indeed. These are two separate patterns. They can have great synergy when used together but it's not a requirement. > it's hard to
2. 2.▲
   by randolorian 5y ago

   Seems like a fundamental misunderstanding to me. Commands get validated via your aggregate, not events. Events are not allowed to be rejected. Ever. Because they already happened.
3. 3.▲
   by randolorian 5y ago

   A proper event storage solution will have optimistic concurrency built in.
4. 4.▲
   by randolorian 7y ago

   I feel like people are running into these problems because they want to pretend that a message broker is an event store. I could try to shovel a star schema into MongoDB too, but why would I want to? Keeping data only in the latest schema i
5. 5.▲
   by randolorian 7y ago

   Why would it? Typically you would have one stream per user.
6. 6.▲
   by randolorian 7y ago

   https://leanpub.com/esversioning/read
7. 7.▲
   by randolorian 7y ago

   Best practices around this have already been established. Most if not all event stores - which Kafka is not - have a concept called 'position.' You save the position atomically along with whatever you did with the message. Then if