Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously to two processors (the main and a standby) and in case of timeout talking to the first we could talk to the second. After the main recovering we could return to the original situation. Maybe we could create both actors in different clusters in different machines to avoid single point of failure in case of machine crash.
Many thanks again for your time and for any comment. Regards. El martes, 18 de marzo de 2014 17:12:43 UTC+1, Patrik Nordwall escribió: > > > I see what you are looking for, and it is not supported with current > tools. It would be something that is periodically replaying the event > stream like a view, but can then be changed into a normal writing processor. > > Have you thought about using an active standby? It would do the exact same > thing as the primary, but the output (external side effects) would be > ignored/filtered on the standby. It depends very much on your domain if > that is a good or bad idea. > > Regards, > Patrik > > >> >> -- >>>>>>>>>> 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.
