I have been building out a POC using event sourcing in order to manage the state of an aggregate root. This works great.
Say I have an aggregate root "Client". I might have thousands of clients in my system (or more). When the user hits my API to say "Get me a list of all clients in the system", or perhaps "Get me a list of all clients in New York", how do I achieve this using an event sourcing model with akka? I haven't found a really good way to do this. For example, what happens when the system cold boots, would I literally have to "boot" every Client aggregate somehow before I can query? Should I keep yet another persistence thing beyond the akka-persistence data store, where I am keeping state twice (which somewhat defeats the purpose of event sourcing)? I am just wondering what others may have done. It feels relatively straightforward to manage the data myself, and skip event sourcing all together. I am sure others have faced this same issue. Thanks! -- >>>>>>>>>> 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.
