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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
