I want to build a service using Akka-HTTP. Let's say that it seems advantageous for this particular service to be able to view the stream of incoming HTTP requests as a *single materialized flow*. Possible advantages for this view are to enable simple batch processing of a stage across multiple concurrent requests (e.g. with groupedWithin), or for backpressure that applies across the service as a whole, rather than just backpressure within each connection (e.g., like mapAsync with the parallelism parameter counting items across all concurrent connections, not just the items within each connection). However, with the IncomingConnection.handleWithXXX methods, Akka-HTTP seems to intend that services be implemented as a *materialized flow per request*, rather than a *materialized flow of requests*.
I'm curious which of these you would say is the case: 1) Akka-HTTP discourages (or does not support) this style of request processing; a materialized flow per connection should be preferred (perhaps for simpler / more robust handling of failures?) 2) Akka-HTTP supports this, but only at a low level, so it's unwieldy to configure, particularly to keep the flow (and the service) running when failure occurs. 3) Akka-HTTP neither supports nor discourages this. Use mapAsync and a custom executor and implement your own batching/aggregation/throttling policies across those connections. 4) It would be more appropriate to use Akka actors for this style of processing. 5) Something else? Thanks in advance, -Dave -- >>>>>>>>>> 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.
