I cannot speak to if it is good actor design or not, I can only speak to my case. Since we are building a large play application (or to be more exact, lots of small services), the way supervision is now makes it impossible to use.
Our goto pattern is usually something along the lines of: Play Controller -> ask to top level entry "singleton" actor -> forward to "singleton" actor in charge of that area -> forward to a per request worker (which may sometimes yet again call other per request actors as needed). (Note: "singleton" here means that we ensure there is only one of those actors, not a true GoF singleton) We were hoping to make the the second singleton a supervisor which will of course will not only be in the spirit of fault tolerance but also tremendously reduce the amount of try-catch-finally code we would need to write. So, to recap, I cannot speak for all of Akka/Actor design, but I think our pattern is a fairly common one coming from Play (Mainly due to that first pesky "ask" I guess). -- >>>>>>>>>> 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.
