Hi Heiko, After reading a bit more about Akka remote, I have a much better understanding of when to use pool and group routers. You mentioned here:
> For pool router, the router needs to send the routee actor to the target > node. > > > No. On the remote system the classes need to be available, no classifies > are transmitted. > > So in this case does that mean the actors that will be deployed need to be in both the local and the remote system. When the router is deployed, it only connects to the same actor class in the remote system. Another question that I have is how can the microservices message each other. On external systems, you use a REST interface, but in an akka cluster/remote that seems a bit overkill. Would you use case classes in this case? Whereby you have the same case class defined in both the local and remote system so they can message each other with actors? Would you use versioning for case classes as well? Regards, Lap -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
