Hi, We use Guice and we got an AkkaModule that creates an ActorSystem and a Materializer that can later on be injected to other classes. I wonder if there is a problem with that. My assumption is that if uses of the actor system, materializer and dispatcer (used as ExecutionContext for Future's) is proper (i.e. all Future's and akka-streams are non-blocking) then it might be OK. But if there is blocking it probably isn't. We do unfortunately have a lot of blocking code in the project (mainly when we query elastic search but on other places too).
Is there any best practice guide on having multiple ActorSystems i.e. in a similar way that ExecutionContexts should be split (cpu intensive tasks, I/O intensive tasks etc)? Thanks -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
