Operators Developers Contributors Reference
Sidebar updates per section — preview limitation
Apache Cassandra

Official Integrations: Sidecar and Analytics

Preview | Unofficial | For review only

Apache Cassandra has two official subprojects that extend cluster operations beyond core Cassandra tooling: Cassandra Sidecar and Cassandra Analytics. This page introduces both projects, explains when operators should consider them, and defines the documentation boundary between Cassandra operator docs and the subproject docs.

For a similar boundary treatment of Kubernetes tooling, see Kubernetes Considerations.

Why These Integrations Exist

Core Cassandra provides nodetool, JMX, and CQL for cluster operations. These tools cover the majority of operator workflows: configuration, repair, compaction, backup, and restore.

However, some operational patterns benefit from capabilities that live outside the core Cassandra process:

  • API-driven lifecycle management — starting, stopping, and querying Cassandra through an HTTP API rather than JMX or SSH

  • CDC pipelines — change data capture with Kafka-oriented configuration

  • Snapshot-backed bulk reads — reading large datasets through Spark without impacting live query traffic

  • Bulk writes with coordinated delivery — writing SSTables to multiple clusters through Sidecar or S3-compatible transport

  • Automated restore workflows — API-driven restore jobs that manage SSTable import and validation

Cassandra Sidecar and Cassandra Analytics are the official Apache Cassandra subprojects that provide these capabilities.

How Sidecar and Analytics Relate

Analytics depends on Sidecar. The Analytics bulk reader and bulk writer use Sidecar endpoints to interact with the target Cassandra cluster.

The correct mental model for operators is:

Cassandra cluster -> Sidecar (operational / API layer) -> Analytics (Spark-based bulk data workflows)

Operators who adopt Analytics must first deploy and secure Sidecar. Operators who only need API-driven lifecycle management, CDC, or restore workflows can adopt Sidecar without Analytics.

When to Consider These Integrations

If you need…​ Consider…​ Instead of…​

API-driven lifecycle management (start, stop, health)

Cassandra Sidecar

Manual nodetool or JMX over SSH

CDC pipelines with Kafka-oriented configuration

Cassandra Sidecar

Custom JMX-based CDC integration

API-driven snapshot and restore workflows

Cassandra Sidecar

Manual nodetool snapshot and sstableloader

Spark-based bulk reads from snapshots

Cassandra Analytics (via Sidecar)

COPY TO or custom export scripts

Bulk writes with S3-compatible transport

Cassandra Analytics (via Sidecar)

sstableloader for large-scale ETL

Coordinated multi-cluster bulk writes

Cassandra Analytics (via Sidecar)

Manual per-cluster sstableloader runs

Compatibility Posture

Cassandra Sidecar and Cassandra Analytics are actively developed official Apache Cassandra subprojects with their own release cadences.

As of the date of this document:

  • Sidecar is designed around multi-version Cassandra support and includes adapters for Cassandra 4.0 and later. The Sidecar public documentation has not yet been updated to explicitly confirm 6.0 support.

  • Analytics includes bridge modules for Cassandra 4.0 and 5.0. The reviewed public materials do not explicitly confirm 6.0 support.

Check the official project repositories for the latest compatibility information before adopting either project.

Project Links

Cassandra Sidecar
Cassandra Analytics

Related Pages

  • Cassandra Sidecar — operator-level orientation for Sidecar adoption, capabilities, and security considerations

  • Cassandra Analytics — operator-level orientation for Analytics bulk read/write workflows

  • Kubernetes Considerations — similar boundary-first guidance for the K8ssandra ecosystem

  • Bulk Loading — core Cassandra bulk loading with sstableloader and nodetool import

  • Backup Strategy — snapshot and backup planning that Sidecar can automate