Hi Thanks a lot to Leonidb for the response.
In this example, the issue itself - as a state machine and its underlying state - is stored in an IssueTracking database (event sourcing). On the other hand, the "name", say John, is written to another database, say NameRegistrationDatabase. Therefore, a two-phase commit-ish is needed to ensure consistency. My question is whether the above requirement can be achieved with actors, with or without PersistentFSM? Please guide me if there are other ways/models to achieve data consistency in this case. In advance thank you very much. -- >>>>>>>>>> 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.
