Hi Paul,
You can indeed use a View to store your data in such a way that it works
for your queries.
With the Akka 2.3.x you need to create a view for every aggregate root
("Client" for your situation). That adds some overhead in handling. (as you
need to trigger these views when changes have happened). The new 2.4
milestone has improvements to solve this situation but I did not have the
time to dive into that yet.
There are other ways to solve your issues, these are all mentioned in this
ticket: https://github.com/akka/akka/issues/16541
On Saturday, August 15, 2015 at 8:48:19 PM UTC+2, Paul Cleary wrote:
>
> I am thinking that the simplest thing is to maintain a separate persistent
> view that gives me query flexibility.
>
> The aggregate root is run via event sourcing.
>
> I try to keep the view in sync, but will update the view whenever the
> aggregate root starts and finishes recovery.
>
> Not sure if there is a better way
>
>
--
>>>>>>>>>> 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.
