Hello, I am building a service which uses Akka Http Client to contact another service and return a Future.
The current architecture result in materializing a stream repeatedly like that: val source = Source single (request, dummy) val result = source via pool runWith Sink.head What impact stream materialization have on performance? Is it more appropriate to replace the stateless service with an actor that holds a Map[CorrelationId, ActorRef] and use the full power of streaming API? Regards Edmondo -- >>>>>>>>>> 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.
