You are awesome! I think that proxy only mode is the trick. The front-end will use proxy only mode, so in essence it really isn't doing much except being busy serving requests, deserializing, all that funness.
The back-end will actually do the hosting of actors. Use a shared library between the front-end and back-end so they can talk (or just have the front-end have a dependency on the backend). This is great stuff, thanks for the quick response! On Friday, March 20, 2015 at 4:29:51 PM UTC-4, Andrey Kuznetsov wrote: > > You can create shard region on frontend in proxy-only mode or pass > messages from frontend to an actor running on backend which will forward > them to shard region. > > On Friday, March 20, 2015 at 10:54:15 PM UTC+3, 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.
