Hi everyone,
i've spent quite some time looking through the akka-streams documentation
but there are still a "few" things i do not seem to grasp (i hope these are
not too much for one thread ...). Assuming, you'd define a graph (of which
each element could either be a simple or rather complex processing state)
such as:
Source.Publisher via deserialize via processBusinessLogic via serialize to
Sink.Subscriber
1. Regarding the mapping to backing actors:
1. How does the standard ActorMaterializer actually map such a graph
(is there any rule set i missed)?
2. Is it possible to influence said mapping without implementing a
completely new Materializer?
3. Is is sensible at all to use the ActorMaterializer or any other
one for an entire application? Or would you rather delegate calls to an
explicitly defined actor hierarchy at some point (e.g. within mapAsync)?
2. Regarding failure handling:
1. Are there any life cycle hooks for processing stages as for
regular actors (e.g. onRestart)?
2. is Subscriber.onError called in every supervision scenario or only
in case of Supervision.Stop?
3. Regarding monitoring:
1. Are there any go-to solutions for finding/ monitoring bottlenecks
(i.e. single processing stages which limit the overall graph throughput)
within a graph?
Thanks for your time & help up front.
Best
Constantin
--
>>>>>>>>>> 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 received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
