Hi Mark, Notice: This mailing list is going to be made read-only shortly, please ask new questions on the: https://discuss.akka.io forum (see footer of every email in this group for details).
Akka Persistence is specifically designed for event-sourcing, and persisting Actor state. If you don’t do that, don’t use Akka Persistence, and simply perform your database operations inside normal actors. As for delivery guarantees — very sure that durable mailboxes only “seem like” they would solve your problem, they would in fact cause more trouble than help — which is why we deprecated and removed them years ago. Instead the https://doc.akka.io/docs/akka/current/persistence.html#at-least-once-delivery at least once delivery is what you would use to achieve at-least once or even exactly once (if de-duplication is implemented on the receiving end). It does use persistence to store the queue of pending messages to survive crashes. -- Cheers, Konrad 'ktoso <http://kto.so>' Malawski Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> On March 15, 2018 at 2:03:01, Mark Kaberman (mkaber...@gmail.com) wrote: I am adding Akka persistence to my existing application. My actors are stateless: actor's implementations have no properties. An actor receives the message, analyzes it and either forwards it to another actor or persists some data (in MongoDB or RDF store). Since actors have no state there is nothing to persist. What I really need is durable mailboxes, but they are deprecated in favor of persistent actors. I am wondering how persistent actor pattern cold be applied to and actor implementation which is essentially a dispatcher and the only goal is not to lose the messages in case of actor system, JVM or host crash. -- ***************************************************************************************************** ** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon. ** This group will soon be put into read-only mode, and replaced by discuss.akka.io ** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced ***************************************************************************************************** >>>>>>>>>> >>>>>>>>>> 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. -- ***************************************************************************************************** ** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon. ** This group will soon be put into read-only mode, and replaced by discuss.akka.io ** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced ***************************************************************************************************** >>>>>>>>>> >>>>>>>>>> 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.
