Hi,
I wanted as well to use ActorPublisher/ActorSubcriber pair. My use case was
related to dynamically scaled number of wokers on a transforming task with
a possible worker failure, restart and redo (based on Work Pulling pattern
by Derek Wyatt
on
Hi Soumya,
I don’t think what you’ll end up measuring this way will be very useful. I
mean, between the completion of the future and the triggering of the map there
are multiple asynchronous boundaries… So you won’t be measuring how fast the
set operation was, but how much time was between
I think I'm clinging to trying to use actors as both publisher and
subscriber because I like actor supervision and I don't see how you do
supervision with streams. Does a custom
Stage / transformer have supervision where exceptions/errors can cause a
restart/resume/escalate that affects a
Hi Mark,
You're completely right a supervision of streams has been on our minds for
a long time now. Sadly you bumped into an yet not implemented area of Akka
streams, here's the issue we're talking about here -
https://github.com/akka/akka/issues/15710
We had multiple talks on how to apply
