I wrote a router that leverages hazelcast logic to execute the action local to
the key and it works but it relies on storing routing information in a
hazelcast map and cleaning it up afterward which in the case of node failure
could have some problems. Obviously we wouldn't want to be sending
So is the strategy I laid out flawed? I don't want to be accessing objects on
the wrong node, that's a critical element of the dynamic. getting Akka and play
to cooperate in cluster is not that hard. I want to make intelligent routing
decisions.
--
Read the docs: http://akka.io/docs/
Hi Robert,
I made an activator template
http://typesafe.com/activator/template/play-akka-cluster-sample for this.
The main point is that your play application
joins the overall akka cluster. You must take care of the linking, what
should be done
locally and what not.
activator new
