These are chat archives for petabridge/akka-bootcamp

30th
Jul 2015
Andrew Skotzko
@skotzko
Jul 30 2015 01:27
@irperez yes, ApiMaster actor is the routee of the router deployed on the Web role.
@irperez Here's what's going on in the Web.config: Web is deploying a group router at /user/tasker, which is then routing the messages it receives on to actors living at path /user/api on nodes marked with the tracker role
@irperez sorry for the delayed response, btw.
Andrew Skotzko
@skotzko
Jul 30 2015 01:44
that group router (/tasker) is local to the Web role process, but it is then using clustering to send its messages across the cluster to the /user/api actors living on tracker roles.
Ivan R. Perez
@irperez
Jul 30 2015 03:55
@skotzko got it! Very cool how this was done!
Ivan R. Perez
@irperez
Jul 30 2015 04:46
@skotzko so there is only one instance of /tasker running? or are there NrOfInstances of /tasker local to web, but just passing on to multiple instances on /user/api (on tracking service)? I'm a little confused. Because in the boot camp, it seems that whatever you instantiate is the routee. No? ActorSystem.ActorOf(Props.Create(() => new RemoteJobActor()).WithRouter(FromConfig.Instance), "tasker"); In this case RemoteJobActor.
Andrew Skotzko
@skotzko
Jul 30 2015 15:38
@irperez IIRC there is just one /tasker per web role. It’s a router, so it’s then sending its messages across the cluster to remote routees.
@irperez in the example you just gave of RemoteJobActor you’re instantiating the routee, yes, but WithRouter => the idea is that the router should be transparent in the middle.
router receives and distributes messages but it’s designed to do so “invisibly”…. ie sender doesn’t need to know it’s there, and routee doesn’t need to know it’s there. (incidentally, this is why the Sender of a message a routee receives from a router is the original sender of the message, not the router. router just Forwards the message, effectively.)