I think your question is more about general integration with Storm. Storm is easily integratable with third-party systems (including Akka) via 'spouts', and there are quite a few queue-based already part of Storm distribution (AMQP, JMS, Kafka etc.). However, giving the fact that Storm and Akka cross-cut on quite a few general concerns around distributed computing/computation it would be nice if you can share a birds eye view of your requirements. May be there is a simpler architecture.
Cheers Oleg On Sun, Feb 2, 2014 at 7:04 AM, Kaizah Kaiser <[email protected]> wrote: > What I am actually trying to do is to have a Storm ( > http://storm-project.net/) cluster talk to a remote Play/Akka web > application. The Play application uses actors for async communication and > now I want to communicate with it from a bolt Storm. Bolts in Storm > however, must be serializable whereas actor systems are not. > > Op vrijdag 31 januari 2014 18:54:59 UTC+1 schreef √: >> >> Hi Kaizah, >> >> On Fri, Jan 31, 2014 at 5:05 PM, Kaizah Kaiser <[email protected]>wrote: >> >>> Hi, >>> >>> I currently have one project that uses Akka 2.2.3 and actors to do stuff >>> in their own actor system (call it server). I now want to make another >>> application (call it client) that communicates with this application _but_ >>> it uses serialization all over the place (this is a hard requirement). The >>> way I usually would do this is by creating an actor system on my client as >>> well and let it retrieve an actorRef for the actor I am trying to reach on >>> server. For this to be possible, I use actorSelection, something that I can >>> only do within an actor system (or am I wrong here?). This however forces >>> me to create an actor system on the client, but actor systems cannot be >>> serialized so I have an issue. >>> >>> I was wondering if there is any way for me to obtain an actorRef of my >>> 'client' without setting up an actor system in it? >>> >> >> I don't udnerstand why you'd have to serialize the actor selection. >> You'll need to run an ActorSystem in the client if you want to connect to >> the server. >> >> >>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>> >>>>>>>>>> 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/groups/opt_out. >>> >> >> >> >> -- >> Cheers, >> √ >> >> * ——————— **Viktor Klang* >> *Chief Architect - **Typesafe <http://www.typesafe.com/>* >> >> Twitter: @viktorklang >> > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> 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/groups/opt_out. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
