【问题标题】:How to combine alpakka kafka with akka stream websocket如何将 alpakka kafka 与 akka 流 websocket 结合使用
【发布时间】:2019-09-02 13:31:20
【问题描述】:

我正在使用https://doc.akka.io/docs/alpakka-kafka/current/consumer.html 来使用来自 kafka 的数据,如下所示:

implicit val system: ActorSystem = ActorSystem("SAPEVENTBUS")
implicit val materializer: Materializer = ActorMaterializer()

val config = system.settings.config.getConfig("akka.kafka.consumer")
val consumerSettings =
  ConsumerSettings(config, new StringDeserializer, new StringDeserializer)
    .withBootstrapServers("localhost:9092")
    .withGroupId("SAP-BUS")
    .withProperty(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "earliest")
    .withProperty(ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG, "true")
    .withProperty(ConsumerConfig.AUTO_COMMIT_INTERVAL_MS_CONFIG, "5000")

val kafkaConsumer =  Consumer
  .plainSource(
    consumerSettings,
    Subscriptions.topics("SAPEVENTBUS"))
  .toMat(Sink.foreach(println))(Keep.both)
  .mapMaterializedValue(DrainingControl.apply)  

接下来,我将收到的结果通过akka http websocket client转发到webserver

如何构建 websocket 客户端:

implicit val system = ActorSystem()
implicit val materializer = ActorMaterializer()
import system.dispatcher

// print each incoming strict text message
val printSink: Sink[Message, Future[Done]] =
  Sink.foreach {
    case message: TextMessage.Strict =>
      println(message.text)
  }

val helloSource: Source[Message, NotUsed] =
  Source.single(TextMessage("hello world!"))

// the Future[Done] is the materialized value of Sink.foreach
// and it is completed when the stream completes
val flow: Flow[Message, Message, Future[Done]] =
  Flow.fromSinkAndSourceMat(printSink, helloSource)(Keep.left)

// upgradeResponse is a Future[WebSocketUpgradeResponse] that
// completes or fails when the connection succeeds or fails
// and closed is a Future[Done] representing the stream completion from above
val (upgradeResponse, closed) =
  Http().singleWebSocketRequest(WebSocketRequest("ws://echo.websocket.org"), flow)

val connected = upgradeResponse.map { upgrade =>
  // just like a regular http request we can access response status which is available via upgrade.response.status
  // status code 101 (Switching Protocols) indicates that server support WebSockets
  if (upgrade.response.status == StatusCodes.SwitchingProtocols) {
    Done
  } else {
    throw new RuntimeException(s"Connection failed: ${upgrade.response.status}")
  }
}

我有两个问题:

  1. 如何将消费者和 websocket 客户端组合成一个流和 让它将消息发送到网络服务器。

  2. 我想将从网络服务器收到的消息广播到 两个接收器,具体取决于内容。

如何构建这样的图?

【问题讨论】:

    标签: scala websocket apache-kafka akka akka-stream


    【解决方案1】:

    如果您打算将所有 Kafka 消息推送到 Web 套接字而不进行响应处理,您应该编写 Web 套接字的消息处理程序 in a true bi-directional scenario where input and output aren’t logically connected

    //Kafka reading logic
    val kafkaSource: Source[ConsumerRecord[String, String], Consumer.Control] = Consumer
        .plainSource(consumerSettings, Subscriptions.topics("SAPEVENTBUS"))
    //kafka message serialization logic
    val kafkaRecordToMessageTransform: Flow[ConsumerRecord[String, String], Message, NotUsed] =
        Flow[ConsumerRecord[String, String]].map[Message](consumerRecord => {
            TextMessage.Strict(s"${consumerRecord.key} - ${consumerRecord.value}")
        })
    
    //web socket's messages sending logic
    val webSocketWriteLogic: Source[Message, Consumer.Control] =
        kafkaSource.via(kafkaRecordToMessageTransform)
    
    //web socket's messages receiving logic
    val webSocketReadLogic: Sink[Message, NotUsed] = Flow[Message].mapAsync[String](1)({
        case textMessage: TextMessage =>
            textMessage.toStrict(collectTimeout).map(_.text)
        case binaryMessage: BinaryMessage =>
            binaryMessage.toStrict(collectTimeout).map(_.data.toString())
    }).to(Sink.foreach[String](messageText => println(s"received $messageText")))
    
    //web socket's logic
    val webSocketLogic: Flow[Message, Message, Consumer.Control] =
        Flow.fromSinkAndSourceMat(webSocketReadLogic, webSocketWriteLogic)(Keep.right)
    

    您可以根据partition stage 的某些条件将流消息广播到多个接收器。另外,您可以查看this explanation

    【讨论】:

      猜你喜欢
      • 2019-05-12
      • 2020-07-29
      • 2017-01-09
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2018-02-16
      • 1970-01-01
      相关资源
      最近更新 更多