@Horusiath, I've been trying Akka.Streams, and I have couple of questions. For example I have this Scala code
override def eventsByTag(tag: String, offset: Long = 0L): Source[EventEnvelope, NotUsed] = {
Source.actorPublisher[EventEnvelope](EventsByTagPublisher.props(tag, offset, Long.MaxValue,
refreshInterval, maxBufSize, writeJournalPluginId)).mapMaterializedValue(_ ⇒ NotUsed)
.named("eventsByTag-" + URLEncoder.encode(tag, ByteString.UTF_8))
}1) What should I use, instead of NotUsed? Unit/Unit.Instanse or something else?
2) I should return Source<EventEnvelope, Unit>, but method "Named" returns IGraph<SourceShape<EventEnvelope>, NotUsed>. How to convert SourceShape<T> to T?
2 Use Source.FromGraph to cast the graph back into a source
@Horusiath Playing with Sharding, I just encountered the following: 2 nodes up, both hosting a region, both processing shard messages. One node leaves cluster, after a few seconds I restart it, it joins the cluster again, but it doesn't receive any shards. The node that didn't shut down keeps on processing all the messages for the entities. So it seems the rebalancing of the shards to the rebooted region doesn't happen?
in case when the difference between number of shards on two machines is too small
This is the sample I'm working on..
I was thinking if they are lightweight enough to use them for agents in a multi agent system.
I would assume though that if you would like to do that you would write your own dispatcher for it.
yes, the are very light in this sence
over a count of 100k you would need to think about memory
i am loading ~1000 per each aggregate root type
and the app has still low memory consumation
messages are short lived and most likly removed on Gen0 GC
world => actor
can be a singleton service t0o, but better an actor
Then you need the sequence of actions of several of the actors.
What is the name of the class i need to look up?
ActorBase
most likly
