Greg, Thank you for responding. I wanted some validation about my design and the selection of my components for the implementation. Based on Andrew's and your response I assume that my basic domain model is correct and I'm moving in the correct direction.
On Tuesday, December 30, 2014 1:03:35 PM UTC-5, Greg Young wrote: > > What exactly is the issue with a single actor controlling an inventory > count? Given that I'm new to akka-persistance and CQRS/ES, I was not sure if this is going to be an issue or not. So just wanted to get some idea before I started with implementing it. > Have you benchmarked any of this or are just getting prematurely wprried? > A quick benchmark here was over 500k/second. With persistence naively was > still >100k. Not yet. I'm working on it right now and will report back once I've some real numbers. Having a quick comparative benchmark really helps. Can you tell which datastore you used for the journal and the snapshot. > You must have a huge number of users to get 100k/s items added to carts! > Correct. I agree, 100k/s is a big number and going beyond that is unlikely. If it goes beyond 100K/s then we can add additional constraints. For example - having sub inventories that get more items from a master inventory on demand. In this case, each sub-inventory actor will be a persistent actor. - by dividing users by geography thanks again for pitching in. -Soumya -- >>>>>>>>>> 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.
