Hi Paul, if your frontend app is going to be deployed outside of the backend cluster you should consider use of Cluster Client (http://doc.akka.io/docs/akka/snapshot/contrib/cluster-client.html) together with Cluster Sharding. I use this pattern in akka-ddd project:
https://github.com/pawelkaczor/akka-ddd/blob/master/akka-ddd-core/src/main/scala/pl/newicom/dddd/cluster/ShardingSupport.scala https://github.com/pawelkaczor/akka-ddd/blob/master/akka-ddd-write-front/src/main/scala/pl/newicom/dddd/writefront/GlobalOfficeClientSupport.scala On Friday, March 20, 2015 at 8:54:15 PM UTC+1, Paul Cleary wrote: > I have two halves of an application, a front-end that is busy with > ingesting data, and a backend for processing the data. > > Is it possible to have the front-end "forward" messages to the back-end > using Cluster Sharding? > > I am interested in Cluster Sharding because I need to be able to have a > single instance of an Actor in the entire cluster and refer to it by a > logical name. Cluster Sharding seems like the way to go for this. > > Ideally, I could: > > ---> http --> FrontEnd -- (look up actor via cluster sharding) --> BackEnd > Actor > > Any ideas, or is Cluster Sharding intended to live inside the same app? > -- >>>>>>>>>> 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.
