I read this tweet from Martin Krasser this morning: "#Akka-persistence is optimized for making stateful actors durable (at very > high transaction rates), not for implementing durable queues"
I am confused as akka-persistence is comparable to other event sourcing solutions<http://doc.akka.io/docs/akka/snapshot/project/migration-guide-eventsourced-2.3.x.html>, which rely on durable queues / journals. So: what exactly is the scope of akka-persistence? Should it just be used for serializing actor state without their mailboxes? This is what I gleaned from the above tweet (retweeted by Jonas). -- >>>>>>>>>> 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.
