I also found this excellent text describing the supervisor hierarchies.
It's about Erlang but the concepts can be applied to Akka
http://learnyousomeerlang.com/building-applications-with-otp#the-onion-layer-theory
On Thursday, 29 May 2014 13:03:03 UTC+1, Jabbar Azam wrote:
>
> Thanks Conrad I
Thanks Conrad I understand.
I think understanding the "error kernel pattern" is really important
together with http://doc.akka.io/docs/akka/2.3.3/general/actor-systems.html
of the documentation.
On Thursday, 29 May 2014 11:48:28 UTC+1, Konrad Malawski wrote:
>
> Not "exactly one", but yeah "a
Not "exactly one", but yeah "as little as possible".
This way of thinking will force your thinking towards creating these
hierarchies of actors which fail or survive together (kind of like the four
musketeers :-)).
And the gains have been outlined already - you are able to fail / restart /
isolate
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, Konr
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
Hello,
I'm a bit confused with supervisor hierarchies. I've read the akka
documentation and other books but hierarchy design is still not sinking in
:(
A simple, made up, example. I have a web front end with business logic and
a database. converting this to akka I would create a
web front en
