<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2581828&amp;fmt=gif">

Platform Home > Data Layer > Data Storage

SQL + Cassandra data storage.

Hybrid relational + time-series storage in one platform - structured MySQL tables alongside high-performance Cassandra, without bolting two databases together.

Workflow-Chain-500

CAPABILITY OVERVIEW

One platform, two databases - no compromise.

Rayven combines MySQL for structured relational data with Apache Cassandra for time-series + event data in a single, unified storage layer.

No ETL pipeline between them. No separate data warehouse. No query tool switch.

Structured records, real-time events, workflow payloads + calculated metrics all coexist in the same platform - governed, queryable + instantly available to dashboards, workflows, AI models + external systems.

Inbound triggers include:

  • All workflow execution data (auto-stored in Cassandra by UID + timestamp)

  • Primary + Secondary Table records (MySQL)

  • Streaming data from IoT, APIs + Kinesis (Cassandra)

  • File-ingested + parsed data

  • Calculated + aggregated metric outputs

Outbound triggers include:

  • Real-time data for dashboards + reports

  • Query-able datasets for API endpoints

  • Training datasets for ML models

  • Raw exports via Node Export + CSV download

  • Data feeds for external systems via output nodes

realtime data processing

KEY CAPABILITIES

What SQL + Cassandra Data Storage gives you.

MySQL for structured relational data

All Primary Tables, Secondary Tables + entity metadata are stored in MySQL. Supports relational queries, joins + structured data management. Familiar SQL patterns, managed entirely within Rayven - no separate database administration required.

Cassandra for time-series + event data

All workflow payload data is automatically stored in Cassandra, indexed by UID, Node ID + Timestamp. Optimised for high-frequency writes, horizontal scalability + low-latency time-series reads - purpose-built for IoT telemetry, event streams + operational logs at any scale.

Hybrid architecture - unified access

MySQL and Cassandra coexist within the same platform layer. Dashboard widgets, workflow nodes + API endpoints query both via the same interface - no tool switching, no cross-database ETL, no schema synchronisation overhead.

Azure-hosted, geo-redundant

Both databases are hosted on Microsoft Azure with geo-redundant storage. Daily automated backups (60-day retention), weekly retention (one year) + monthly retention (three years). No single point of failure. Consistent performance regardless of geographic distribution.

Automated backup + retention policies

Daily backups run automatically with 60-day retention by default. Weekly + monthly retention extends historical coverage for compliance + audit. Data Repository node settings configure per-workflow retention at the workflow level.

Instant data availability

Data written to either database is immediately queryable. No refresh cycle, no replication delay, no batch sync. Dashboard auto-refresh operates on live data. API endpoints return current state. AI models train on up-to-date datasets.

HOW IT CONNECTS: EXPLAINER

Where SQL + Cassandra Data Storage fits in the Rayven Platform stack.

The storage layer underpins every other capability in the platform - all data from the Integration Layer is stored here before any downstream use.

  • Data from the Integration Layer flows into MySQL (structured records) or Cassandra (event + time-series data) immediately on ingestion.

  • The Execution Layer reads from both stores for workflow logic, AI + automation.

  • The Presentation Layer queries both for dashboards, reports + custom interfaces.

  • API endpoints expose data from either store to external systems on demand.

Data storage is invisible to end users - it simply ensures data is always there, always current, always accessible.

USE CASES

How SQL + Cassandra Data Storage gets used.

Hybrid data model for an industrial AI platform

A mining operator stores asset registry records in MySQL Primary Tables and continuous sensor telemetry in Cassandra indexed per-asset + timestamp. Workflow logic queries MySQL for asset metadata and Cassandra for the latest sensor values within the same execution chain - no cross-database orchestration required.

GenAI-Solution-500

Financial services BI platform without a data warehouse

A financial services firm stores customer profiles + contract records in MySQL Secondary Tables and transaction event logs in Cassandra. Live dashboard widgets query both simultaneously - structured customer data alongside real-time transaction metrics. No data warehouse, no ETL delay.

Cash-Forecast-Solution-WebP

Partner-operated multi-client platform on shared infrastructure

An MSP runs multiple clients on a single Rayven instance. Client entity records are stored per-Label in MySQL. Client event data is stored per-UID in Cassandra with Label-based access control. Both stores are isolated by Label - clients access only their own data. One infrastructure, full data governance.

Tables-Page-500

Rayven SQL + Cassandra Data Storage FAQs:

MySQL excels at structured relational data - queries, joins, entity records + reference tables. Cassandra excels at high-frequency writes, time-series data + distributed horizontal scalability. Using both in a hybrid model means each database handles the workload it was designed for - without performance compromises.

No. Both databases are fully managed by Rayven's infrastructure team. Schema management for MySQL tables is handled through the platform UI. Cassandra is managed automatically - data is indexed by UID + timestamp on write, with no manual schema management required.

Cassandra scales horizontally as data volume grows - adding nodes maintains performance as datasets expand. MySQL scales within standard relational database parameters. For very large-scale deployments, contact us to discuss the appropriate configuration for your data volumes.

Immediately. Data written to Cassandra or MySQL is available to workflow queries, dashboard reads + API endpoint responses without delay. There is no synchronisation lag, no replication wait time + no batch refresh cycle.

Daily automated backups run across both databases with 60-day retention by default. Weekly backups are retained for one year. Monthly backups for three years. Backup schedules + retention periods are configurable for compliance requirements.

Yes. All data in both MySQL and Cassandra is encrypted at rest using AES-256. Data in transit is encrypted via 256-bit SSL. Encryption is applied at the infrastructure level - no additional configuration required.

Cassandra uses CQL rather than SQL. Within Rayven, all querying of Cassandra data is handled through workflow nodes + dashboard widgets - you do not interact with the Cassandra query layer directly. The Query Tables node provides SQL-like querying of MySQL tables within workflows.

Yes. Node Export downloads raw Cassandra workflow data for any node + time range. CSV export is available for MySQL table data via the platform UI. For automated exports, Output to FTP + Output to HTTP (webhook) nodes push data to external destinations on a schedule or trigger.

Label-based access control segregates client data within shared database infrastructure. Each client's data is tagged with their Label on ingestion - workflow triggers, dashboard queries + API endpoints filter by Label, ensuring each client accesses only their own records across both databases.

Cassandra's distributed architecture replicates data across multiple nodes - if one node fails, data remains accessible from replicas. MySQL is hosted on Azure with high-availability configuration. Both databases are designed for no single point of failure.

Engineering-Leader-vertical WebP

Join the Shift

Discover the easy way to do something new.

Book a demo with our team and we'll show you exactly how Rayven can work for your environment.