Hello, I have a simple Play application that does some statistical analysis of data and alerts customers with alerts when something is wrong. Sometimes it happens, that sending alert fails (SMTP server down, network errors) etc.
I was thinking of a way to make the email sending process more resilient by using some features of Akka Persistence (I'm quite new here), so the workflow I was considering: 1. Persistent actor receives request to send email alerts. 2. Alerts are persistence with akka persistence plugin. 3. Alerts are sent by the actor. However, the problem I see in this is that if Actor crashes and replays all messages I would send duplicates (or worse) of emails, so I would have to clear the messages myself, which kind of misses the point of using actor at all. Is Persistent Actor the right approach to solve these kind of problems? Should I solve this problem the `default` way by just using some external storage for all non-sent mails (e.g. Kafka queue)? -- >>>>>>>>>> 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.
