On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote: > > > > The User actor persist FirstNameChanged, and inside the persist block it > sends a Persistent(FirstNameChanged) message to the AllUsers Processor. On > the query side we have a AllUsersView connected to that processor. When > AllUsersView receives FirstNameChanged it updates the db table. > > To handle lost messages between User and AllUsers you might want to send > an acknowledgement from AllUsers to User, and have a retry mechanism in > User. I would implement that myself in User, but PersistentChannel might be > an alternative. > > That is the most straight forward solution. The drawback is that > FirstNameChanged is stored twice. >
What's wrong with the following (push only) solution (much more simple): User (eventsourced actor) ---- reliable event delivery (Channel) ---> AllUsers (normal actor, updates projection (i.e sql table)) Pawel > -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
