Skip to main content

When to use Cassandra vs. CockroachDB

Apache Cassandra has become a core element of most modern data architectures and in this video we'll explore when to use a NoSQL database like Cassandra and when you need the transactional consistency of a distributed SQL database like CockroachDB. It scales and allows you to get data where you need it for some distributed workloads. It was architected to meet these requirements but traded speed of access for other characteristics. So, not every distributed workload fits Cassandra. What happens with Cassandra when you need transactional consistency or continuous updates to your application data? These workloads require a database that not only delivers effortless scale but will also deliver transactional guarantees. This is where CockroachDB fits. In this webinar, we will walk through workloads and where each database can deliver value for your workloads by walking through: Key architectural differences between Cassandra and CockroachDB When to pick CockroachDB over Cassandra How CockroachDB can deliver on your “system of record” requirements 00:00 Speaker Introductions 5:50 Quick history of Cassandra 6:30 Why is Cassandra called Cassandra? 6:59 What companies use Cassandra? 8:30 How does Cassandra work? 10:14 Query first architecture 11:36 What is CockroachDB? 15:22 How database replication works 16:06 Hash partitioning vs range partitioning 21:54 How scale works in Cassandra 24:09 How does Cassandra survive failure 27:16 Problems in Cassandra 30:50 How CockroachDB employs RAFT 35:25 What is CQL? 40:24 Transactions in Cassandra 43:45 Time travel queries 48:38 Data Locality 56:35 When to use cassandra Links Referenced in the webinar: Netflix Tech Blog: The architecture of Distributed SQL: Compare Cassandra & CockroachDB: --------------------------------------------------------------------------------------------------------------------------- Careers: CockroachCloud: CockroachDB: Blog: Docs: Community Slack: