Clustering the supervisors feels wrong. The entity we have a lot of is the
ChannelMonitor, and one message may have several ChannelMonitor
destinations. The eventbus with lookup classification works great in the
non-distributed scenario.
What's the overhead of topics in DistributedPubSub? Can we h
On Tue, Jul 21, 2015 at 10:56 PM, Richard Rodseth
wrote:
> I'd love a little more input on this, being a complete neophyte when it
> comes to Akka cluster.
>
> To recap, let's call this entity ChannelMonitor. There are many many
> ChannelMonitors underneath a ChannelMonitorSupervisor.
> Currently
I'd love a little more input on this, being a complete neophyte when it
comes to Akka cluster.
To recap, let's call this entity ChannelMonitor. There are many many
ChannelMonitors underneath a ChannelMonitorSupervisor.
Currently, a message pertaining to a particular channel gets from the
superviso
But I'll take a look, thanks. Not sure if one topic per channel is feasible.
On Fri, Jul 10, 2015 at 9:04 AM, Richard Rodseth wrote:
> Nope. I imagined it to be for broadcasting, rather than having something
> analagous to LookupClassification.
>
> On Fri, Jul 10, 2015 at 12:16 AM, Jim Hazen
>
Nope. I imagined it to be for broadcasting, rather than having something
analagous to LookupClassification.
On Fri, Jul 10, 2015 at 12:16 AM, Jim Hazen wrote:
> Tried looking at the DistributedPubSub module?
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the
Tried looking at the DistributedPubSub module?
--
>> 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 receive
We're not using Akka Cluster yet, but I have an entity actor type that is
ripe for sharding.
But there's a complication. The numerous entities are receiving event data
for various "channels", and rather than receiving messages directly from
the supervisor, the supervisor publishes them to an Event
