On Fri, Feb 21, 2014 at 10:49 AM, <[email protected]> wrote: > If I want to update say 5 of these documents in a single transaction then > are you suggesting I have one actor responsible for all 5? >
Think of it this way: if you want to update all 5 of them in the same transaction, that implies that there is *some* semantic relationship that ties them all together -- a higher-level collection, or a common User, or something of the sort. The best way to handle this situation in Akka is typically to represent that relationship as an Actor, and put the transactional update in there. Remember, Actors don't have to be mutually-exclusive, and interesting Actor systems are rarely single-level. It's very common to have a hive of cooperating Actors working together, in charge of different semantic aspects of a complex problem... -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
