I use persistent actors in order to accomplish at-least-once message guarantee and it seems Akka uses Leveldb for persisting events to disks. However I'm not actually satisfied with default journal implementation because while it has the obvious performance drawbacks, I couldn't really understand what the real benefit is. I have a web server in front of Akka and the persistent actor lives in the same JVM with web server. Therefore if the JVM crashes, users will be aware that the server couldn't process the event so JVM failures is not a big deal for me.
I see that people are suggesting in-memory journals for unit testing so I assume that using it in production is considered as a bad practice. I know that Apache Storm also has at-least-once message guarantee and it doesn't persist each event on disk but many companies uses Storm in production without worrying too much about this issue. Can anyone explain why Akka persist messages on disk and what are the other drawbacks of using in-memory journal? -- >>>>>>>>>> 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.
