IoT & edge ingestion

Surgewave's typical IoT shape: thousands of devices push readings via MQTT to the gateway, downstream analytics and AI pipelines consume from the same Surgewave topic via the Kafka wire — one event log, two access patterns, no protocol bridge.

Architecture

flowchart LR
    Devices[devices]
    Gateway[Surgewave gateway]
    Analytics["analytics, AI, archive"]
    Kafka["Kafka clients on :9092"]
    Streams["Streams topology"]
    Tier["S3 / Azure tier"]

    Devices -->|MQTT 5.0| Gateway
    Gateway -->|topic| Analytics
    Gateway --> Kafka
    Gateway --> Streams
    Gateway --> Tier

Why Surgewave fits

  • MQTT in, Kafka out — same topic, two wire protocols. No bridge service to maintain. See MQTT transport.
  • Embedded broker for the edge — Kuestenlogik.Surgewave.Broker runs in-process on edge gateways. See embedded mode.
  • QUIC for unreliable links — 0-RTT resumption keeps cellular and Wi-Fi-roaming devices connected. See QUIC transport.
  • Tiered storage — last 24 h on hot disk, history on cheap object storage. See the tiered-storage guide.

Sample

Kuestenlogik/Surgewave.Samples/IotDashboard walks through an end-to-end gateway-broker-dashboard setup with simulated device traffic.

Edit this page