Apache Cassandra & comparison to DynamoDB

Jun 24 · 1 min read

This blog lists links that I referenced while comparing and understanding the differences between the two:

Architecture and data modeling for Cassandra (Or DSE — DataStax) looks quite similar.

Data modeling based on the query (access) pattern and denormalization is a common theme to achieve super fast responses.

Data in DataStax Enterprise is often arranged as one query per table, and data is repeated amongst many tables, a process known as denormalization. Relational databases instead normalize data, removing as much duplication as possible.

Some good blogs for delving more into those:

Useful Comparison study:

Interesting to note that the concept of partition key in C8 is same as the Hash key in DynamoDB. Similarly, clustering columns in C8 is similar to the Range key (Sory Key) in DynamoDB.

Some questions I had:

  1. Why can’t we query for =null or != null in either of the databases?
  2. What is the max number of “clustering columns” in Cassandra?
  3. Why would you create secondary index instead of clustering columns in Cassandra?


My technical posts mostly on Java backend services


Written by

Software Engineer working on Java based Micro-services deployed on AWS cloud. California, US resident currently — born and brought up in Bangalore, India.


My technical posts mostly on Java backend services

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade