Quite a read on a phone during my holidays. Very insightful and adds a lot of 
considerations around the different topics. 

I'd like to mention that the current construct of the persistent view is very 
helpful in decoupling. I can create new listeners (e.g. PersistentView) based 
on the events persisted in the store. 

Tags were proposed and I would be using those to actually attach the aggregate 
root type to the event so my persistent views would use that to 'read' the 
events and create the model. That model is used for the queries in the 
application (or for other purposes) 

At this moment, I persist all changes on a an aggregate root (persistent actor 
for a specific instance) by writing a changed event with a specific 
persistenceId in the payload (of the aggregate root) to a generic persistenceId 
and use that to create a persistent view that uses the specific aggregate root 
Id as persistenceId (discussed in another group topic). 

When tags are not the way forward, there is a need for some kind of 
query/resolver mechanism that allows to define what the persistentview is 
listening to. In my use case, the persistent actor is a cluster sharded actor 
and the persistenceId is actually the unique identifier of an instance of an 
aggregate root. My view would want to listen to the all events persisted by 
this type of aggregate root. (So that meta data needs to be available too) 

Kind regards,

Olger

Btw: repost, sloooow internet in the mountains. 

-- 
>>>>>>>>>>      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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to