Getting Data from Beacon Tower
Three ways to get processed asset data out of Beacon Tower — choose based on your use case.
Data Egress Methods
| Method | Best For | Latency | Protocol |
|---|---|---|---|
| MQTT Publishing | System-to-system integration, IoT consumers | Low | MQTT |
| SignalR Streaming | Web dashboards, browser-based UIs | Low | WebSocket |
| REST API | Historical queries, batch analysis, reporting | Request-based | HTTP |
MQTT Publishing
The MQTT Publisher publishes asset telemetry and diagnostics to an MQTT broker. Backend services register subscriptions via a REST API, and the Asset Processor routes matching data through NATS to the Publisher for delivery.
Best for backend integrations, analytics pipelines, and any system that already speaks MQTT.
SignalR Streaming
SignalR Streaming pushes real-time asset data and alarm updates over WebSocket connections. Clients negotiate a connection, subscribe to specific assets, and receive live updates without polling.
Best for browser-based dashboards, monitoring UIs, and applications that need instant visual feedback.
REST API
The REST API provides historical timeseries queries, latest values, and asset state over HTTP. Supports aggregation, pagination, and bulk queries.
Best for reporting, batch analysis, and applications that query on demand rather than streaming continuously.