Apache Cassandra
change data capture
TwinCommit captures changes from Apache Cassandra by reading its transaction log directly, then delivers each committed transaction exactly once to any supported target. Commit-log CDC from every node, deduplicated into one ordered stream.
Apache Cassandra
Apache Cassandra 4.0, 4.1, 5.0 · DataStax Enterprise 6.8+ · Astra DB (target) · ScyllaDB (target)
- ✓cdc_enabled: true in cassandra.yaml
- ✓WITH cdc = true on replicated tables
- ✓Agent sidecar or shared volume access to cdc_raw on each node
Capture
How TwinCommit reads Cassandra
TwinCommit tails the CDC commit-log segments on every node, deduplicates replica writes, and orders mutations by write timestamp per partition.
Cassandra source docs →Apply
How TwinCommit writes to Cassandra
Batched upserts and deletes use the source commit timestamp as the Cassandra write timestamp, so replays are idempotent and newer data always wins.
Cassandra target docs →Replicate Cassandra to…
Cassandra connector FAQ
Which Cassandra versions does TwinCommit support?
+
Apache Cassandra 4.0, 4.1, 5.0 · DataStax Enterprise 6.8+ · Astra DB (target) · ScyllaDB (target).
Does TwinCommit install anything in Cassandra?
+
No. TwinCommit reads the Cassandra log and creates no triggers, tables or procedures in the source database.
How does TwinCommit write to Cassandra?
+
Batched upserts and deletes use the source commit timestamp as the Cassandra write timestamp, so replays are idempotent and newer data always wins.
Replicate your first table in five minutes.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.