On Monday, January 19, 2015 at 11:00:03 AM UTC-5, Ashesh Ambasta wrote: > > Thank you for the time you've put in for the detailed replies Soumya & As. > Well, I think your reply has me convinced and the more research I put in > for Akka, the more ideal it seemed for our use case. In short, our > architecture is like this: > Glad to help.
> > *CORE API *(Play + Scala) <–> *PUSH* (Akka + Scala) ... and some other > microservices. What is a little concerning is the fact that we would like > to pass around model class objects to the Push service, and these should be > the same as in the Core. We don't want to replicate any kind of code, and > only the API data pushing logic should reside in the Push service. > If you need to pass data from core to your push API I don't see how you can do that without passing your model classes. I think you avoid code replication by sharing repositories (your model classes) if nothing changes between layers. > > Moreover, I'm yet to be clear on how Akka remoting works. The Push service > shall reside on a separate machine altogether and the Core service should > be able to talk to it over the network. It seems a bit magical that you can > reference actors from across the network without actually *import*ing > anything. If I can get more clarity on that, it'll be helpful. > I think you will find all your answers in the Akka documentation. http://doc.akka.io/docs/akka/snapshot/scala/remoting.html Good luck. -Soumya -- >>>>>>>>>> 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.
