Greetings,
I am working on some tech to integrate hazelcast and Akka. The thing is
with Hazelcast, a particular object in the cache may be on any one of the
nodes in the cluster and serializing the object from its host node to the
node in the cluster where it is being processed can be expensive. So I was
debating an alternative paradigm. Basically I was considering storing the
actor refs to the Actor in the hazelcast map keyed by the member id. The
idea is I ask the map "Give me the actor ref for node 3" and it returns
back an ActorRef object and then the router uses that to forward the
message to the correct router on the correct node via a normal call. For
example:
def forward(msg: Object, key: Object) = {
val uuid =
hazelcast.getPartitionService().getPartition(key).getMember().getUuid()
hazelcast.getMap("RoutingActors").get(uuid) ! msg
}
Can anyone see any issue with such a paradigm? Do I have to tell hazelcast
that the actor ref is on another node? Do I need to open any ports or do
any other configuration to get such a thing to work?
Thanks.
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
