On Tuesday, 19 August 2014 19:33:55 UTC+8, Martin Krasser wrote: > > If so, it sounds like a great solution but why would that require an > extension to the Akka Persistence design/API? > > > Because transformed/joined/... event streams in backend store on the read > side must be consumable by PersistentViews (for creating read models). I > still see this backend store to maintain changes (= transformed/joined/... > events) instead of current state. >
I am sorry I still don't see this. This suggests to me that spark is talking directly to the read model datastore (e.g. graph database, MongoDB, SQL database). So are you suggesting: 1. journal -> spark -> Akka actors (like PersistentView) -> read model data store or 2. journal -> spark -> read model data store (like graph database, MongoDb, SQL database) -> Akka actors <- Queries I see PersistentView(for generalised topics) as the glue between the Akka journal (write store) and read stores (1.). Thanks for your patience. Cheers, Ashley. -- >>>>>>>>>> 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.
