These are chat archives for RBMHTechnology/eventuate

15th
Mar 2017
kant
@kant111
Mar 15 2017 02:15
Hi, I am new to event sourcing but I'm trying to grasp the concepts quickly. I understand that event sourcing is all about storing events that represents changes in the state but not the state itself. so In my case, I get messages from Kafka and each message is encoded in JSON with 50 fields like this {key1: val1, key2: val2, .......key50: val50} and every message will have all or subset of these keys. Now my goal is to store these stream of messages as events in Cassandra and for me to store the changes in state I always need to know the current state to see the change in state caused by the next request but I wonder how this is done or more importantly how the data in the datastore would like?