Edge Messaging & Brokers
8 entriesBrokers and protocols that move device data.
Edge Stream Processing
9 entriesEngines that filter, enrich and analyse data in motion.
Edge Platform Runtimes
2 entriesCloud-managed edge runtimes.
Telemetry Collectors & Pipelines
6 entriesAgents that collect and forward data.
Related Pages
9 entriesRelated directories on this site.
Frequently Asked Questions
What is edge-based streaming analytics?
It is processing continuous streams of events, such as sensor readings and logs, on or near the devices that produce them, so filtering, aggregation and alerts happen before the data travels to a central cloud.
How is it different from cloud streaming analytics?
Cloud streaming platforms such as Kafka, Flink and managed streaming services run in data centres and handle very large aggregated streams. Edge streaming runs in constrained, often disconnected locations and sends only useful results upstream.
Do I still need a cloud streaming platform?
Usually yes. Edge streaming reduces and reacts to data locally, while a cloud platform handles aggregation across sites, long-term storage and model training. See the Streaming Analytics Platforms directory.
Why are MQTT brokers on this list?
MQTT is the dominant protocol for device telemetry, and brokers with rule engines or local routing are often the first stage of an edge streaming pipeline.
What hardware is needed?
The tools here range from single binaries that run on small gateways to agents that run on single-board computers and fuller platforms for industrial PCs. Check each project's resource requirements.
How do I choose an approach?
Start with the data source. For MQTT devices pick a broker with a rule engine, for simple collection use a lightweight collector such as Telegraf or Fluent Bit, and for filtering or windowed analysis on the device use a stream processor such as eKuiper or a flow tool such as Node-RED.