DynamoDB vs MongoDB vs Cassandra - When to Use Which

The Big Idea

What if your data could organize itself and respond instantly to your needs?

The Scenario

Imagine you have a huge collection of customer data spread across multiple spreadsheets and text files. You try to find specific customer details or update records manually every time someone calls. It's like searching for a needle in a haystack without any tools.

The Problem

Doing this by hand is slow and mistakes happen easily. You might update the wrong file, miss some data, or lose track of changes. As your data grows, it becomes impossible to keep everything organized and accurate without a system.

The Solution

DynamoDB, MongoDB, and Cassandra are powerful database systems designed to store and manage large amounts of data efficiently. They let you quickly find, update, and organize data without manual searching. Each has unique strengths to handle different needs, making data management smooth and reliable.

Before vs After

✗ Before

Open spreadsheet -> Search customer -> Edit details -> Save file

✓ After

db.collection.find({customerId: 123}) -> db.collection.updateOne({customerId: 123}, {$set: {details}})

What It Enables

These databases enable fast, reliable, and scalable data handling that supports real-time applications and massive data growth.

Real Life Example

An online store uses DynamoDB to instantly retrieve product info for millions of customers worldwide, MongoDB to store flexible user profiles, and Cassandra to handle huge streams of sales data without delays.

Key Takeaways

Manual data handling is slow and error-prone.

DynamoDB, MongoDB, and Cassandra automate and speed up data management.

Choosing the right database helps your app scale and stay reliable.

Practice

1. Which database is best known for automatic scaling and simple key-value access?

easy

A. Cassandra

B. DynamoDB

C. MongoDB

D. MySQL

Solution

1. Step 1: Understand DynamoDB's core feature

   DynamoDB is designed for simple key-value access and automatic scaling.

2. Step 2: Compare with other databases

   MongoDB focuses on flexible document storage, Cassandra on high availability for huge data.

3. Final Answer:

   DynamoDB -> Option B

4. Quick Check:

   Automatic scaling + key-value = DynamoDB [OK]

Hint: Automatic scaling with key-value means DynamoDB [OK]

Common Mistakes:

• Confusing MongoDB's flexible documents with key-value simplicity
• Thinking Cassandra automatically scales like DynamoDB
• Choosing MySQL which is relational, not key-value

2. Which of the following is the correct way to describe MongoDB's data model?

easy

A. Column-family store with automatic partitioning

B. Simple key-value pairs with fixed schema

C. Flexible document storage with rich queries

D. Relational tables with strict schema

Solution

1. Step 1: Identify MongoDB's data model

   MongoDB stores data as flexible JSON-like documents allowing rich queries.

2. Step 2: Eliminate other options

   Column-family store describes Cassandra, key-value with fixed schema fits DynamoDB less, relational tables fit SQL databases.

3. Final Answer:

   Flexible document storage with rich queries -> Option C

4. Quick Check:

   MongoDB = flexible documents + rich queries [OK]

Hint: MongoDB = flexible JSON documents + rich queries [OK]

Common Mistakes:

• Confusing MongoDB with Cassandra's column-family model
• Thinking MongoDB uses fixed schema like relational DB
• Mixing key-value with document storage

3. Given a large dataset requiring high availability and fast writes across multiple data centers, which database is most suitable?

medium

A. MongoDB

B. DynamoDB

C. SQLite

D. Cassandra

Solution

1. Step 1: Analyze requirements for high availability and multi-datacenter writes

   Cassandra is designed for huge data with high availability and multi-region replication.

2. Step 2: Compare other options

   MongoDB supports replication but less optimized for huge scale multi-datacenter writes; DynamoDB is scalable but less focused on multi-datacenter writes; SQLite is local and not distributed.

3. Final Answer:

   Cassandra -> Option D

4. Quick Check:

   High availability + multi-datacenter = Cassandra [OK]

Hint: Huge data + multi-region writes = Cassandra [OK]

Common Mistakes:

• Choosing DynamoDB for multi-datacenter writes
• Confusing SQLite as distributed database
• Assuming MongoDB handles huge multi-region writes best

4. You try to use MongoDB's flexible document queries on DynamoDB but get errors. What is the likely cause?

medium

A. DynamoDB does not support flexible document queries like MongoDB

B. DynamoDB requires SQL syntax for queries

C. MongoDB uses column-family data model incompatible with DynamoDB

D. DynamoDB only supports relational tables

Solution

1. Step 1: Understand query capabilities of DynamoDB

   DynamoDB supports key-value and simple queries but not rich flexible document queries like MongoDB.

2. Step 2: Eliminate incorrect causes

   DynamoDB does not use SQL syntax, is not column-family, and is not relational.

3. Final Answer:

   DynamoDB does not support flexible document queries like MongoDB -> Option A

4. Quick Check:

   DynamoDB lacks MongoDB's flexible queries [OK]

Hint: DynamoDB lacks MongoDB's rich document query support [OK]

Common Mistakes:

• Assuming DynamoDB uses SQL syntax
• Confusing data models between MongoDB and Cassandra
• Thinking DynamoDB supports relational tables

5. You need a database for an app that requires flexible JSON documents, automatic scaling, and global availability. Which approach best fits this need?

hard

A. Use DynamoDB with JSON support and global tables

B. Use MongoDB with sharding and replica sets only

C. Use Cassandra with column-family tables and no JSON support

D. Use SQLite with local JSON extensions

Solution

1. Step 1: Identify features needed

   The app needs flexible JSON documents, automatic scaling, and global availability.

2. Step 2: Match features to databases

   DynamoDB supports JSON documents, automatic scaling, and global tables for availability. MongoDB supports JSON but global availability requires extra setup and scaling is manual. Cassandra lacks native JSON support and SQLite is local only.

3. Final Answer:

   Use DynamoDB with JSON support and global tables -> Option A

4. Quick Check:

   JSON + auto scale + global = DynamoDB [OK]

Hint: DynamoDB global tables + JSON = best for scaling + availability [OK]

Common Mistakes:

• Choosing MongoDB without considering scaling complexity
• Ignoring Cassandra's lack of JSON support
• Selecting SQLite which is not distributed