This blog lists links that I referenced while comparing and understanding the differences between the two:
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:
Basic Rules of Cassandra Data Modeling
Learn more about Apache Cassandra and data modeling READ MORE DS:220 COURSE Picking the right data model is the hardest…
A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications
Today marks the 10 year anniversary of Amazon’s Dynamo whitepaper, a milestone that made me reflect on how much…
Useful Comparison study:
Amazon DynamoDB vs Apache Cassandra
Cassandra and DynamoDB both origin from the same paper: Dynamo: Amazon’s Highly Available Key-value store. (By the way…
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:
- Why can’t we query for =null or != null in either of the databases?
- What is the max number of “clustering columns” in Cassandra?
- Why would you create secondary index instead of clustering columns in Cassandra?