*Awesome*. This is exactly the answer I was looking for, Ryan!
I need to read and re-read your post a couple more times for it to sink in,
but this seems like a great starting point. A blog article on this topic
would really be appreciated, though! :- )
I'm of the opinion that while Typesafe
Glad to help!
On Wednesday, January 7, 2015 3:53:28 AM UTC-7, Kane Rogers wrote:
*Awesome*. This is exactly the answer I was looking for, Ryan!
I need to read and re-read your post a couple more times for it to sink
in, but this seems like a great starting point. A blog article on this
Hi Kane,
Exploring the different options, one limitation that I can see is that
ClusterPoolRouter requires the class of the actor that's going to be
remotely deployed to the cluster to be *present on the class path of the
router. *That is, if our front-ends are to create a worker on a
We're also deploying an Akka cluster on CoreOS with Docker. We deploy the
same fat JAR for every node (in fact, the exact same docker image) and then
change their behavior by setting the role via environment variables.
In our case, each role has a bootstrap class which sets up whatever
