Hi guys, simple question: is it expected that exactly 1 PersistentActor that makes use of a specific persistenceId is active ?
In order to get all changes of my AggregateRoot, I've build a publisher that tells that this aggregate has changed. By using a single persistenceId, it's possible to read for all instances of the aggregate and thereafter fire up a specific view for the specific AggregateRoot. (nothing new here, all discussed in other threads) My idea was to build an extension for that as that is a nice and usable way to publish these changes. Side effect is that every actor system that actually does the domain for this aggregate (and with cluster sharding, it is expected to be more than 1) will run such a publisher actor (that is actually a PersistentActor). This gives 'strange' behaviour around the persistence sequence numbers (actually counting per live actor system) that made me wondering if this approach appropriate. I've got the feeling that the answer is 'yes', still handy to have it here for the record. Kind regards, Olger -- >>>>>>>>>> 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.
