How Rayven supports real-time data processing, IoT integration, and high-frequency time series applications.
Overview
Rayven is designed from the ground up to support real-time, time series, and IoT-based applications. These capabilities are not add-ons—they are core to how the platform processes, stores, and presents data. Whether your use case involves sensor telemetry, high-frequency transaction data, or dynamic control systems, Rayven provides the infrastructure and toolkit to build responsive, scalable, and data-rich solutions.
This page introduces the foundational capabilities that enable these types of solutions, and shows how Rayven’s real-time architecture, workflows, and interface options come together to support high-performance applications.
Real-time Architecture in Rayven
Rayven’s ability to support real-time applications stems from a combination of architectural choices and workflow design features:
-
Cassandra time series database
Rayven uses Cassandra to store all data that flows through workflows. This database is optimised for time series storage, allowing efficient write/read operations even under high-frequency data loads. -
Structured and unstructured storage layers
Structured data (managed via Primary and Secondary Tables) is stored in MySQL. Time series data (e.g. streaming sensor values) is stored in Cassandra and automatically indexed by UID, Node ID, and Timestamp. -
Workflow-level data execution
Workflows execute instantly when triggered by data arriving from external systems or internal events. Workflows can process data one row at a time, for a subset of rows, or for every record in a Primary Table—enabling scalable, iterative logic.
IoT and Streaming Data Support
Rayven includes native support for a broad range of IoT data protocols and connector types, such as:
-
MQTT, Modbus, LoRaWAN, SNMP, and Raw UDP, for edge and industrial devices
-
HTTP, API, AWS Kinesis, and FTP for streaming and batch ingestion
-
Forms and UI interactions for manual or human-entered inputs
These connectors allow Rayven to integrate with almost any real-time source—whether it's a low-power sensor, a programmable controller, or a cloud-based streaming API.
Iterative and Device-Aware Workflows
Rayven workflows are designed to respond immediately to incoming data. Whenever data is received—from an API, a sensor, a user form, or another workflow—the workflow will run with that payload. This means if 100 assets are sending data individually, the workflow will execute separately for each incoming packet, as it arrives.
In addition to this real-time responsiveness, you can also configure workflows to run iteratively across:
-
Each Primary Table UID
Execute logic per asset, sensor, or record—for example, evaluating rules per machine. -
Each Label Value
Run logic grouped by categories like site, zone, or region. -
Once per trigger event
For scheduled or event-based workflows that don’t need per-record processing.
This flexibility enables workflows to scale across asset fleets or user datasets, while maintaining tailored logic per entity or group.
Use cases include:
-
Monitoring individual assets for performance thresholds
-
Calculating and comparing metrics across locations
-
Running control logic per machine, sensor, or input group
Widgets for Real-time Monitoring
Rayven’s prebuilt widgets are designed to visualise real-time and historical data without requiring custom development. Available widgets include:
-
Single value, gauge, tank level, and multi-value indicators
-
Line charts, multi-line charts, bar charts, timeline charts, pie charts, and more
-
Map and heatmap visualisations for location-related data
-
Image overlays and custom UI Code widgets for visual or domain-specific interfaces
These widgets update automatically based on the workflow data feeding them. Refresh rates and filtering options are configurable in the node settings.
Analytics Interfaces for Time-Filtered Views
For time series analysis, Rayven supports Analytics Interfaces. These pages allow users to select a time range and view only data from that window. Only supported widgets can be added to these interfaces—ideal for exploring trends or generating reports.
Example Use Cases
Rayven’s real-time and IoT capabilities are widely applicable. Here are a few typical examples:
-
Utility Meter Monitoring
Stream meter readings every few seconds, trigger alerts on anomalies, and visualise performance by region. -
Fleet Tracking
Process GPS and telemetry data per asset, show location in real time on a map, and maintain a historical timeline of movements. -
Industrial Equipment Oversight
Collect and visualise machine health metrics (temperature, pressure, vibration), and trigger workflows when thresholds are breached. -
Environmental Dashboards
Aggregate sensor readings (e.g. weather stations), group by zone, and present summaries to users via front end interfaces.
Summary
Rayven provides a robust foundation for building real-time, high-volume, and device-aware applications. Its architecture combines dedicated time series storage, flexible workflows, and native support for common IoT protocols, enabling scalable and responsive solutions. Whether you’re monitoring sensor data, processing streaming events, or building interactive operational interfaces, Rayven equips you with the tools to configure, automate, and visualise data in real time.
FAQs
Can I ingest data from physical sensors or field devices?
Yes. Rayven supports industrial protocols like MQTT, HTTP, Modbus, and LoRaWAN for this purpose.
Do dashboards update automatically?
Yes. All analytics and data widgets in Rayven will refresh automatically, typically every 30 seconds, without requiring a manual reload.
Can workflows handle thousands of devices?
Yes. Workflows can iterate across UIDs, making it possible to build logic that scales across hundreds or thousands of assets.
How do I configure time-based views?
Use an Analytics Interface. These interfaces provide built-in date range selectors to filter historical data views.
Can I visualise location-based data?
Yes. The Map node can display location data based on either the UID (e.g. asset or device) or a Label Value (e.g. customer or site). For UIDs, location can be set as a static attribute in the Primary Table or dynamically updated from incoming data payloads. You can also configure the map to show historical paths or movement traces for mobile assets.
Is this only for industrial use cases?
No. Rayven is a flexible application development toolkit suitable for a wide range of use cases—from logistics, utilities, and smart infrastructure to customer-facing applications and internal business tools. Its ability to process real-time data, configure interactive interfaces, and integrate with external systems makes it applicable across many sectors, not just industrial environments.