I have a system that is a traditional DB centric app for the most part. However the data is loaded in a memcache for speed and ease of use. What I would be interested in doing is migrating the app to a actor centric paradigm. Also keep in mind that I speak Scala but my colleagues don't so I would have to be stuck in Java world. The use case I can't get past is this.
A user has an entry in a competition and if they win the competition they get a prize. When we want to award that user a prize we need to go update the entry noting it has been paid, write multiple transactions to the system to track the payment and update their wallet with the prize. Now all of these things have to happen or none of them have to happen. It would make sense to make the entry an actor as well as the wallet. The transactions are a bit more questionable. What I can't figure out is how I can change all of those actors and fail if anything goes wrong. There is no option to think that we can avoid ACID here. I have been researching on google and this group and there is a lot of information but most is dated and conflicting. Any ideas to help out? -- >>>>>>>>>> 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.
