if my current state A = {key1: val1, key2: val2, .......key50: val50} and
the next state B = {key1: val1, key2: val2, .......key5: val5} then
Persistence actor would store A-B = {key6: val6, key7: val7, .......key50:
val50} ?
On Tuesday, March 14, 2017 at 10:20:42 AM UTC-7, kant kodali wrote:
>
> Thanks for all the replies. When I first came across event sourcing it
> clearly says one stores events and changes in the state but not the state
> itself. so In my case, I get messages from Kafka and each message is say
> 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
> typically with PersistenceActor? Any simplistic example would help a great
> deal!
>
>
>
> On Sunday, March 12, 2017 at 7:09:06 AM UTC-7, kant kodali wrote:
>>
>> Hi,
>>
>> What does it mean when someone says we store the event itself rather than
>> storing the state/data? such that the events can be replayed to store the
>> state/data. Does it mean storing the functions/transformation itself
>> (simply put the JVM byte code for the function itself) ?
>>
>> Thanks!
>> kant
>>
>
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
