The ScyllaDB Connector
Archive ScyllaDB tables and datasets at the point of application migration or compliance mandate. Preserve high-throughput operational data in open Lakehouse format — without ScyllaDB infrastructure.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
ScyllaDB Archiving — Done Right
ScyllaDB’s compaction and TTL mechanisms are designed to purge data — that is a feature for operational workloads and a liability for compliance. Financial time-series, IoT event streams, and user activity logs stored in ScyllaDB may carry SEC 17a-4, MiFID II, or GDPR retention obligations that outlast any TTL value you have configured.
Archon’s ScyllaDB Connector intercepts data before TTL expiry and archives tables, keyspaces, materialized views, and TTL-expiring records into open Parquet/Delta Lake format — immutably, permanently accessible without ScyllaDB infrastructure.
- Tables, keyspaces, materialized views, secondary indexes, TTL-expiring records, audit logs via CQL protocol (Cassandra-compatible driver)
- ScyllaDB 4.x, 5.x, 6.x and ScyllaDB Enterprise supported
- Cross-table query via Archon Analyzer — no ScyllaDB runtime post-archive
- SEC 17a-4, FINRA, MiFID II, GDPR, and IoT regulatory mandates supported
Capabilities
Everything You Need for ScyllaDB Data Operations
Full schema and historical data extraction
All ScyllaDB tables, materialized views, and schema structures extracted with relational integrity and column-level metadata preserved. No custom extraction scripts or database administrator involvement required.
TTL-expiry interception
Archon extracts data on configurable schedules aligned to TTL windows — ensuring compliance-relevant records are captured before ScyllaDB's compaction process removes them. Critical keyspaces can be configured for continuous extraction.
Application retirement and infrastructure cost elimination
ScyllaDB instances retained solely for compliance data access decommissioned after archiving. Licensing and infrastructure costs eliminated while regulatory compliance is maintained.
Compliance audit trail support
Audit tables, transaction logs, and schema-level metadata preserved in the Archon archive — satisfying SEC 17a-4, FINRA, MiFID II, GDPR, and IoT regulatory mandates, accessible without ScyllaDB infrastructure.
Use Cases
How Enterprises Use the ScyllaDB Connector
01 Financial time-series compliance archiving
Fintech and financial services organizations storing transactional time-series in ScyllaDB archive that data before TTL expiry — satisfying SEC 17a-4 and MiFID II Article 25 record retention requirements.
02 IoT and operational event log preservation
IoT platforms with device event streams and operational logs in ScyllaDB archive those records through Archon — satisfying sector-specific data retention mandates without extending ScyllaDB infrastructure.
03 License and infrastructure cost elimination
ScyllaDB instances running solely for compliance access decommissioned after Archon archives the data. Licensing, support, and infrastructure costs eliminated.
04 Compliance audit and eDiscovery support
Compliance audits and legal proceedings requiring ScyllaDB records from prior years fulfilled through Archon Analyzer — without database administrator involvement or a live ScyllaDB instance.
Technical Specifications
| Specification | Details |
|---|---|
| Connection | ScyllaDB CQL protocol / Cassandra-compatible driver |
| Supported Versions | ScyllaDB 4.x, 5.x, 6.x; ScyllaDB Enterprise |
| Data Scope | Tables, keyspaces, materialized views, secondary indexes, TTL-expiring records, audit logs |
| Output Format | Parquet, Delta Lake, Avro, XML, CSV, TXT, TSV, Excel |
| Metadata Handling | Schema structure, indexes, constraints, column definitions, TTL values |
| Transformation Rules | 1,000+ built-in; ScyllaDB data type normalization included |
| Retention Management | SEC 17a-4, FINRA, MiFID II Article 25, GDPR Article 5, IoT mandates |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · WORM · Cryptographic hashing |
How It Works
Up and Running in 4 Steps
01
Connect to ScyllaDB
Authenticate via ScyllaDB CQL protocol to ScyllaDB 4.x–6.x or ScyllaDB Enterprise. Archon auto-discovers all databases, schemas, tables, views, and TTL configurations.
02
Map & Configure
Define schema and table scope, TTL-aware extraction schedules, data type normalization rules, and jurisdiction-specific retention schedules. Configure PII masking for GDPR compliance.
03
Validate & Preview
Dry-run against sample ScyllaDB databases. Quality report flags null primary keys, TTL expiry risks, and data type normalization issues.
04
Archive & Monitor
Cryptographic hashes and trusted timestamps applied per table. Data searchable via Archon Analyzer on ingestion.FAQ
Common Questions About the ScyllaDB Connector
-
1. Does Archon support ScyllaDB without requiring DBA involvement?
Yes. Read-only CQL protocol extraction — no administrative privileges or custom extraction code required.
-
2. Is archived ScyllaDB data queryable without the ScyllaDB runtime?
Yes. Open Parquet/Delta Lake format — queryable via Archon Analyzer, Apache Spark, Amazon Athena, or any Lakehouse query engine.
-
3. Can Archon archive ScyllaDB without impacting live application performance?
Yes. Read-only connections with configurable parallelism and throttle settings — zero production impact during extraction.
Ready to archive your ScyllaDB data and retire the dependency?
Talk to an Archon connector specialist at archondatastore.com. Free consultation, no commitment, reply within 24 hours.
