1. Concepts and Reference Architectures
9 entriesWhat edge data analytics is and where processing should happen. Analyse close to the source when latency, bandwidth, privacy or connectivity demand it.
2. Data Collection, Messaging and Telemetry Pipelines
16 entriesGathering, filtering and forwarding data from devices and applications at the edge. Filter and aggregate early to save bandwidth.
3. Edge Stream Processing, Rules and Portable Runtimes
9 entriesCompute that runs on gateways and small servers. Pick engines that fit the memory and CPU budget.
4. Edge Databases, Storage and Sync
12 entriesLocal stores for buffering, querying and syncing data. Design for intermittent connectivity and conflict resolution.
5. Edge Inference, Vision and Online Learning
12 entriesRunning models next to the data. Optimise models for the target hardware and monitor drift.
6. Edge Platforms, Orchestration and Fleet Management
16 entriesDeploying and operating analytics across many sites. Treat edge fleets with the same GitOps discipline as cloud clusters.
7. Security, Privacy and Regulation
13 entriesProtecting data and workloads on distributed, physically exposed hardware. Edge nodes are easier to reach physically, so assume less trust.
8. Related Pages on This Site
20 entriesDirectories for edge platforms, IoT, analytics and AI. Where each layer of an edge analytics stack is listed.
Frequently Asked Questions
What is edge data analytics?
Edge data analytics processes and analyses data on or near the devices, gateways and local servers that produce it, instead of sending everything to a central cloud first. It filters, aggregates, scores and acts on data locally, and sends summaries, alerts or training data upstream.
Why analyse data at the edge?
The main reasons are latency for real-time control, reduced bandwidth and cloud costs, working through unreliable connections, keeping sensitive data local for privacy or sovereignty, and resilience when the network is down.
How is edge analytics different from cloud analytics?
Edge nodes have limited compute, memory, power and sometimes physical security, run in many scattered locations and may go offline. Edge designs therefore favour lightweight engines, local buffering and sync, remote management and models optimised for the hardware, with the cloud used for heavy training and fleet-wide analysis.
What does an edge analytics architecture look like?
Typical layers are devices and sensors, a gateway or edge server for protocol translation and filtering, a local broker and stream engine, a local database or buffer, optional model inference, secure uplink to the cloud, and a management plane for deployment, monitoring and updates.
Which tools are common at the edge?
Common choices include MQTT brokers such as EMQX, Mosquitto and NanoMQ, NATS or Zenoh for messaging, eKuiper or Flink for stream processing, DuckDB, SQLite or time-series databases for storage, LiteRT, ONNX Runtime or OpenVINO for inference, and K3s, KubeEdge or EdgeX Foundry with GitOps for operations.
How do I handle disconnected operation and sync?
Buffer data locally with durable queues or a database, use store-and-forward or MQTT bridging, design idempotent uploads, and consider local-first approaches with conflict-free replicated data types such as Automerge for data edited in more than one place.
What are the security and privacy concerns?
Edge hardware can be physically accessed, so use device identity, secure boot, encryption, signed updates and zero trust principles. Techniques such as federated learning and differential privacy reduce raw-data movement, and laws such as GDPR, India's DPDP Act, the EU Data Act and the Cyber Resilience Act may apply.
How current is this list?
Links were checked in November 2026. Some sites block automated checks and may need a manual click. This page is a resource list, not engineering advice. For vendor solutions, see the Edge Data Analytics Solutions page.