On Fri, Oct 20, 2017 at 8:22 AM, Bertil Muth <bertil.m...@hood-group.com> wrote:
> That would mean that developing such an application could be quite > different from developing a local application, > where state is spread over many objects. (Or rather, the only way to > change state in another object would be that > the other object is an Actor as well and it receives an event that is > raised. But what if it does not receive the event > during replay? Wouldn't that corrupt the overall state of the application?) > In such a situation, that other Actor would typically *also* be Persistent. That's kind of the point of Actor-centric design: each Actor is responsible for its own bit of state. I find that it's not at all unusual to have a lot of different Persistent Actors... -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
