ou probably shouldn't worry about, but it's good to understand
> what's happening underneath.
>
> -Michael
>
> On 01/20/16 00:17, Karthik Deivasigamani wrote:
>
> Hi,
>I have a use case where I have to pass message between actors and send
> a response back to the caller
Hi,
I have a use case where I have to pass message between actors and send a
response back to the caller.
Once I get a request I invoke Actor A, which will do some DB call and
return results. But in certain cases actor A has to invoke actor B and get
some results from Actor B. It then has
t think you can
>> achieve what you described.
>>
>> Heiko
>>
>> --
>>
>> *Heiko Seeberger*
>> Home: heikoseeberger.de
>> Twitter: @hseeberger <https://twitter.com/hseeberger>
>> Public key: keybase.io/hseeberger
>>
>> On
Hi,
I have been using cluster sharding feature in akka 2.4.1. I would like
the sharding to be topology aware. For example : if I have a cluster with
nodes - n1,n2,n3,n4. If my request goes to node n1 and if the entity actor
does not exist in the cluster then it must create the entity actor
> Cheers,
> Konrad 'ktoso’ Malawski
> Akka @ Typesafe
>
> On 2 December 2015 at 04:31:34, Karthik Deivasigamani (karthi...@gmail.com)
> wrote:
>
> Konrad,
> Does cluster sharding feature require the actors to be persistent
> actors? I looked at the typesafe examples
a/current/scala/cluster-sharding.html
>
> Such "to the same Actor, given an identifier" is exactly what it is
> designed for.
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> Akka <http://akka.io> @ Typesafe <http://typesafe.com>
>
> On 28 Novemb
We have a system where we require all requests pertaining to a given
user-id be processed in order and by the same actor. For example : if we
get requests for userid - u1,u2,u3,u1,u4,u5,u5 in that order then the
requests for user-id u1 must always go to the same actor so that they can
