Database Reference
In-Depth Information
be scaled, while in Cassandra Cluster, it's a multistep as well as multihour process. In Dy-
namo DB, scale-down is also better and much less time consuming, with low latency.
DynamoDB has the capability to insert or delete an item from a set without using complex
code. Its operational cost will be zero as, once we set up backup jobs at specific time in-
tervals, there is no need to manage the database, no disk space monitoring, no need to
check memory usage, and no need to replace or repair the failed node. DynamoDB saves
costs too. Cassandra basically supports a logically unlimited amount of data at a time with
a specific key. This means that this limit is up to the disk space on a particular node, but
DynamoDB's limit is up to 64 KB, so it might be tricky to handle overflow. Cassandra
supports transactions very well by delivering ACID compliance using a commit log to
capture all read and write operations, with built-in redundancy that ensures data durability
if the hardware fails.
Now take a look at the tabular comparison between these two databases:
Specification
DynamoDB
Cassandra
Data model
Key-value store
Key-value with wide column store
BSD
Linux
Operating system
Cross platform (hosted)
OS X
Windows
License
Commercial (Amazon)
Commercial(Apache)
Data storage
Solid-state drive (SSD)
Filesystem
Secondary indexes Yes
No
API call
CQL
(short for
Cassandra Query
Language
)
Accessing method
API call
Apache Thrift
Server-side script
No
No
