Cluster Sharding takes care of rebalancing automatically, and if the
default strategy is not enough you can plug in your own.
As for redundancy/durability you have to save the state of the entity
actors somewhere. Many use Akka Persistence for that but you can use
something else.
/Patrik
On Fri,
Hi Konrad,
Thanks for the pointers.My data is in tree like structure.Potentially the
there can have millions of tree node objects. Akka distributed data does
not fit, I cannot afford to have tree data distributed across all the
cluster nodes. Assuming one cluster node can handle 1 million tre
Welcome to Akka.
Firstly, Hazlecast and Akka are not really the same beast. Akka is not
"just a cache", it's active entities doing things - i.e. Actors, similar to
like Erlang works with processes.
So it may help to change the mindset a bit, since it's not a cache. It can
however model very similar
Hi,
I am new to akka. I used Hazelcast before. In hazelcast cluster the
framework takes care of cluster auto re balancing, auto store n copies (n
is configurable) of back up data on different nodes, Hazelcast executor
service allows me to send a task to the "keyOwner" which allows me to have
