I have an akka-http api that, upon receiving requests, sends messages to my
Cluster via the cluster sharding region. The API layer doesn't know the
ActorRefs of the actors in question, just the string identifiers.
region ! AddTarget(sourceId, targetId)
So Cluster Sharding works by looking up
)
Thanks,
Curt Siffert
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>
Regarding that suggestion, here is a code sample on how you might
accomplish the case of a graph stage that registers for updates from an
actor:
https://github.com/Keenworks/SampleActorStage
Curt Siffert
On Thursday, June 8, 2017 at 4:27:43 AM UTC-7, Akka Team wrote:
>
> One way
Here’s a code sample showing a possible usage of getStageActor.
https://github.com/Keenworks/SampleActorStage
<https://github.com/Keenworks/SampleActorStage>
> On Jun 4, 2017, at 12:12 PM, Curt Siffert <c...@keenworks.com> wrote:
>
> I believe I have figured this
from the callback
function. I will link to a code sample for others looking for a smaller
getStageActor example after I clean it up a bit.
Curt
> On Jun 2, 2017, at 9:15 PM, Curt Siffert <c...@keenworks.com> wrote:
>
> I made some progress figuring out how to us
l.com>>:
> In case it helps:
>
> https://groups.google.com/d/topic/akka-user/AgVHHnl9ub4/discussion
> <https://groups.google.com/d/topic/akka-user/AgVHHnl9ub4/discussion>
> https://github.com/akka/akka/issues/22742
> <https://github.com/akka/akka/issues/22742>
>
&g
Hi, I see in the docs for 2.5.2 that ActorPublisher/ActorSubscriber will be
deprecated.
In my (still beginning) experiments with akka streams I used ActorPublisher
as a way to help create some back pressure controls while consuming
messages from an external queue. This worked just by
> On Apr 22, 2017, at 9:12 AM, Justin du coeur wrote:
> Personally, I'd likely use Akka Cluster Sharding for this -- assuming each
> request can be summarized in a way that fits as an entity identifier, it
> seems like a good fit. In this model, the sharded entity would
Hi, I have a simple use case where a service:
- reads from a queue
- uses that information to make a call to an external web service
- caches those results to Redis so it doesn't need to make that external
call every time
- uses those results to send modified information to another queue
In the
Hi, when discovering seed nodes dynamically, why is it important for every
node (except for one) to not include itself in the seed node list? How
could split brain happen if all nodes have the same list order of all seed
nodes?
>From what I understand, split-brain can only happen if multiple
Not sure if this is a classic pattern, but it seemed pretty
straightforward, and didn't require any changes to actual workings of our
Master/Worker systems.
Curt
On Friday, March 18, 2016 at 12:56:43 AM UTC-7, Curt Siffert wrote:
>
> Hi, I'm supporting a pre-existing Akka project that
Hi, I'm supporting a pre-existing Akka project that is currently set up to
run 1 Master instance and N Worker instances.
It does not use routing/remoting. We start them in 'Master' or 'Worker'
modes via startup flags - each instance has its own actor system, and the
only information they
12 matches
Mail list logo