NoSQL vs relational database comparison in DynamoDB - Visual Side-by-Side Comparison

Concept Flow - NoSQL vs relational database comparison

Start

↓

Choose Database Type

↓

Relational DB

↓

Tables with Rows

↓

Fixed Schema

↓

Use SQL Queries

↓

Strong ACID

↓

Good for Complex

↓

Relationships

↓

End

This flow shows the choice between relational and NoSQL databases, highlighting their structure, schema, query style, consistency, and use cases.

Execution Sample

DynamoDB

-- Relational DB example
SELECT * FROM Users WHERE Age > 30;

-- NoSQL (DynamoDB) example
aws dynamodb scan --table-name Users --filter-expression "Age > :age" --expression-attribute-values '{":age":{"N":"30"}}'

This shows a simple query to get users older than 30 in both relational SQL and DynamoDB NoSQL style.

Execution Table

Step	Database Type	Structure	Schema	Query Style	Consistency	Use Case
1	Relational	Tables with rows and columns	Fixed schema (defined columns)	SQL queries	Strong ACID (Atomicity, Consistency, Isolation, Durability)	Good for complex relationships and transactions
2	NoSQL (DynamoDB)	Tables with items (key-value pairs)	Flexible schema (attributes can vary)	API calls or query expressions	Eventual consistency by default, can be configured for strong consistency	Good for big data, high scalability, flexible data models
3	Relational	Rows must follow schema	Schema changes require migrations	Joins supported	Transactions supported	Structured data with relations
4	NoSQL (DynamoDB)	Items can have different attributes	Schema changes easy, no migrations needed	No joins, denormalization common	Limited transactions (ACID in some cases)	Unstructured or semi-structured data
5	Relational	Scaling vertically (bigger servers)	Schema enforces data integrity	Complex queries possible	Strong consistency always	Financial, ERP, CRM systems
6	NoSQL (DynamoDB)	Scaling horizontally (more servers)	Flexible for evolving data	Simple queries, no complex joins	Eventual consistency for speed	Web apps, IoT, real-time analytics
7	End	-	-	-	-	-

💡 Comparison ends after listing key differences and use cases for both database types.

Variable Tracker

Aspect	Relational DB	NoSQL (DynamoDB)
Structure	Tables with rows and columns	Tables with items (key-value pairs)
Schema	Fixed, predefined columns	Flexible, attributes vary per item
Query Style	SQL language	API calls or expressions
Consistency	Strong ACID	Eventual by default, optional strong
Scaling	Vertical scaling	Horizontal scaling
Use Case	Complex relationships, transactions	Big data, scalability, flexible data

Key Moments - 3 Insights

Why does NoSQL allow flexible schema while relational databases do not?

Because NoSQL stores data as items with varying attributes (see execution_table rows 2 and 4), it does not require all data to fit a fixed column structure like relational tables do (rows 1 and 3).

How does consistency differ between relational and DynamoDB NoSQL?

Relational databases guarantee strong ACID consistency (rows 1 and 5), while DynamoDB defaults to eventual consistency for speed but can be configured for strong consistency (rows 2 and 6).

Why are joins common in relational but not in NoSQL?

Relational databases support joins to combine tables (row 3), but NoSQL databases like DynamoDB do not support joins and instead use denormalized data to avoid complex queries (row 4).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is it mentioned that NoSQL uses flexible schema?

A Step 2

B Step 3

C Step 1

D Step 5

💡 Hint

Check the 'Schema' column for NoSQL in step 2.

According to variable_tracker, which database type uses vertical scaling?

A NoSQL (DynamoDB)

B Relational DB

C Both

D Neither

💡 Hint

Look at the 'Scaling' row in variable_tracker.

From execution_table, which database type supports complex joins?

A Both

B NoSQL (DynamoDB)

C Relational DB

D None

💡 Hint

See the 'Query Style' and 'Use Case' columns in step 3.

Concept Snapshot

NoSQL vs Relational Databases:
- Relational: fixed schema, tables with rows/columns, SQL queries, strong ACID consistency.
- NoSQL (DynamoDB): flexible schema, key-value items, API queries, eventual consistency by default.
- Relational scales vertically; NoSQL scales horizontally.
- Use relational for complex relationships; NoSQL for big data and scalability.
- NoSQL avoids joins; relational supports them for complex queries.

Full Transcript

This visual execution compares NoSQL and relational databases. It starts by choosing the database type, then shows relational databases have fixed schemas with tables and rows, using SQL queries and strong ACID consistency. NoSQL databases like DynamoDB have flexible schemas with items that can vary, use API calls for queries, and offer eventual consistency by default. Relational databases scale vertically and are good for complex relationships and transactions, while NoSQL scales horizontally and suits big data and flexible models. Key differences include schema rigidity, query style, consistency guarantees, and scaling methods. Joins are supported in relational but not in NoSQL, which uses denormalization instead. This helps beginners see the practical differences and when to use each type.