您的问题非常开放，因此我将对您的要求做出一些假设。
请求假设：由于某个事件而产生了很多请求。
创建一个包含封装 async-http-client (https://github.com/sonatype/async-http-client) 的 Actor 的路由器。一旦 async-http-client 完成一个请求，它就会向协调参与者发送一条消息，该消息的 ID 包含在 Req Ack 中。协调参与者将聚合 ID。
以下大部分是伪代码，但它与真正的 API 足够接近，您应该能够找出缺失的部分。
case class Request(url:String)
case class IDReceived(id:String)
case class RequestingActor extends Actor {
override def receive = {
case Request(url) => {
//set up the async client and run the request
//since it's async the client will not block and this actor can continue making generating more requests
}
}
}
class AsyncHttpClientResponseHandler(aggregationActor:ActorRef) extends SomeAsyncClientHandler {
//Override the necessary Handler methods.
override def onComplete = {
aggregationActor ! IDReceived(//get the id from the response)
}
}
class SomeEventHandlerClass {
val requestRouter = actorSystem.actorOf(Props[RequestingActor].withRouter(FromConfig(//maybe you've configured a round-robin router)), requestRouterName)
def onEvent(url:String) {
requestRouter ! Request(url)
}
}
case class AggregationActor extends Actor {
val idStorage = //some form of storage, maybe a Map if other information about the task ID needs to be stored as well. Map(id -> other information)
override def receive = {
case IDReceived(id) => //add the ID to idStorage
}
}
响应假设：您需要对响应中包含的数据做一些事情，然后将 ID 标记为完整。 HTTP 前端只需要处理这一组消息。
不要试图找到一个与 Akka 集成的框架，只需使用一个简单的 HTTP 前端，它将消息发送到您创建的 Akka 网络。我无法想象使用 play-mini 获得的任何优势，而且我认为它会掩盖一些描绘工作分离和控制的界限。情况并非总是如此，但鉴于您的问题缺乏要求，我没有其他可依据的意见。
case class ResponseHandlingActor extends Actor {
val aggregationActor = actorSystem.actorFor(//the name of the aggregation router within the Actor System)
override def receive = {
case Response(data) => {
//do something with the data. If the data manipulation is blocking or long running it may warrant its own network of actors.
aggregationActor ! ResponseReceived(//get the id from the response)
}
}
}
class ScalatraFrontEnd() extends ScalatraServlet {
val responseRouter = actorSystem.actorOf(Props[RequestingActor].withRouter(FromConfig(//maybe you've configured a round-robin router)), requestRouterName)
post("/response") {
responseRouter ! Response(//data from the response)
}
}
创建一个与此类似的系统可以很好地分离关注点，让您很容易推断处理发生在哪里，并有足够的空间来扩展或扩展系统。