Hello Konrad, I had read the relevant documentation but I still couldn't work out the structure of the actor hierarchies. Does this mean that there you should only have one actor which is the child of the user guardian, or am I missing something?
On Wednesday, 28 May 2014 23:24:08 UTC+1, Konrad Malawski wrote: > > Hello Jabbar, > In general try to prefer creating deeper hierarchies instead of flat ones. > I like to demonstrate this on a bit more finer granularity than in the > above example: let's say your actor represents a piece of work (maybe a web > request), and it's coordinating some work, which it's children execute. > When one dies (let's say the DB underneath it has died) you can then > *there* decide how to handle this - by for example killing all other > actors, since you won't be able to compute the end-result anyway with this > one guy dead. > > I assume you have read through the examples on fault > tolerance<http://doc.akka.io/docs/akka/2.3.3/scala/fault-tolerance.html>from > the docs already. > I think that the diagrams for the fault > tolerance<http://doc.akka.io/docs/akka/2.3.3/scala/fault-tolerance-sample.html>example > are esp. helpful to see how this all fits together - it highlights > an recovery / auto-healing scenario. > > I hope this helps, cheers! > > -- > Cheers, > Konrad 'ktoso' Malawski > hAkker - Typesafe, Inc > > <http://scaladays.org> > -- >>>>>>>>>> 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.
