Why database choice impacts architecture in HLD - Why This Architecture

Problem Statement

Choosing the wrong database can cause system slowdowns, data loss, or inability to scale. For example, a database that cannot handle high write loads will bottleneck the entire application, causing poor user experience and failures under peak traffic.

Solution

Selecting a database that fits the data model, query patterns, and scale requirements ensures smooth operation. The right database supports efficient data storage, fast queries, and reliable transactions, which shapes the overall system design and performance.

Architecture

Application

→Database

↓

Query Patterns

──────────────┘

↓

Data Model

─────────────────────────────────────┘

This diagram shows how the application interacts with the database, which depends on the data model and query patterns. The database choice affects storage and retrieval, influencing the entire architecture.

Trade-offs

✓ Pros

→

Optimizes performance by matching database strengths to workload types.

→

Improves scalability by choosing databases that handle expected data volume.

→

Enhances reliability with databases supporting required consistency and durability.

✗ Cons

→

Wrong choice can cause costly refactoring later.

→

Some databases have limited query flexibility or transaction support.

→

Complexity increases when mixing multiple database types.

Use when system requirements include specific data models (e.g., relational, document), query patterns, or scale beyond thousands of requests per second.

When the system is a simple prototype or proof of concept with minimal data and low traffic, complex database choice may be unnecessary.

Real World Examples

Netflix

Uses Cassandra for high write throughput and availability in user viewing history storage, enabling smooth streaming experiences.

Uber

Uses MySQL for transactional data requiring strong consistency, and Redis for fast caching to handle real-time ride matching.

Amazon

Uses DynamoDB for scalable key-value storage to support massive e-commerce traffic with low latency.

Alternatives

Polyglot Persistence

Uses multiple database types specialized for different parts of the system rather than a single database.

Use when: When different data types and workloads require optimized storage and querying beyond one database's capabilities.

In-memory Databases

Stores data primarily in RAM for ultra-fast access, differing from disk-based databases.

Use when: When extremely low latency is critical and data size fits in memory.

Summary

Database choice directly affects system performance, scalability, and reliability.

Matching database features to data and query patterns shapes the overall architecture.

Poor database selection can cause costly redesigns and system failures.

Practice

1. Which of the following is a primary reason why the choice of database impacts system architecture?

easy

A. Database choice only matters for small systems

B. All databases use the same query language

C. Databases do not affect system performance

D. Different databases handle data consistency and scaling differently

Solution

1. Step 1: Understand database roles in architecture

   Databases store and manage data, affecting how data is accessed and maintained.

2. Step 2: Recognize differences in consistency and scaling

   Relational and NoSQL databases differ in consistency guarantees and how they scale horizontally or vertically.

3. Final Answer:

   Different databases handle data consistency and scaling differently -> Option D

4. Quick Check:

   Database choice affects consistency and scaling [OK]

Hint: Focus on how data handling varies by database type [OK]

Common Mistakes:

• Assuming all databases behave the same
• Ignoring scaling differences
• Thinking database choice doesn't affect performance

2. Which database type is best described by this syntax for creating a table: CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(100));?

easy

A. Document-based NoSQL database

B. Key-value store

C. Relational SQL database

D. Graph database

Solution

1. Step 1: Identify the syntax style

   The CREATE TABLE statement with columns and types is standard SQL syntax.

2. Step 2: Match syntax to database type

   Relational databases use SQL and tables with defined schemas.

3. Final Answer:

   Relational SQL database -> Option C

4. Quick Check:

   SQL table creation = Relational database [OK]

Hint: Look for SQL keywords like CREATE TABLE [OK]

Common Mistakes:

• Confusing NoSQL with SQL syntax
• Assuming all databases use SQL
• Ignoring schema definitions

3. Consider a system using a NoSQL document database storing user profiles as JSON. Which architectural impact is most likely when scaling this system?

medium

A. Easier horizontal scaling with eventual consistency

B. Strong ACID transactions across multiple documents

C. Rigid schema enforcement for all data

D. Limited ability to shard data across servers

Solution

1. Step 1: Understand NoSQL document database traits

   NoSQL document stores often allow flexible schemas and scale horizontally.

2. Step 2: Identify scaling and consistency trade-offs

   They usually provide eventual consistency and support sharding for horizontal scaling.

3. Final Answer:

   Easier horizontal scaling with eventual consistency -> Option A

4. Quick Check:

   NoSQL scaling = horizontal + eventual consistency [OK]

Hint: NoSQL means flexible schema and horizontal scaling [OK]

Common Mistakes:

• Expecting strong ACID transactions in NoSQL
• Assuming rigid schemas
• Thinking sharding is limited

4. A system architect chose a relational database but faces performance issues with high write loads. What is a likely architectural mistake?

medium

A. Using eventual consistency instead of strong consistency

B. Ignoring NoSQL options that scale writes better

C. Choosing a key-value store for complex joins

D. Not using SQL queries for data retrieval

Solution

1. Step 1: Analyze the problem context

   Relational databases can struggle with very high write loads due to ACID constraints.

2. Step 2: Identify architectural mistake

   Ignoring NoSQL databases that handle high write throughput with eventual consistency is a common error.

3. Final Answer:

   Ignoring NoSQL options that scale writes better -> Option B

4. Quick Check:

   High write load needs scalable DB choice [OK]

Hint: High writes? Consider NoSQL for better scaling [OK]

Common Mistakes:

• Assuming relational DB always best
• Confusing consistency models
• Misusing key-value stores for complex queries

5. You are designing a global social media platform requiring fast reads, flexible user data, and eventual consistency. Which database choice best fits this architecture and why?

hard

A. NoSQL document database for flexible schema and horizontal scaling

B. Graph database for user relationships but no horizontal scaling

C. In-memory key-value store only for all data storage

D. Relational database for strong consistency and complex joins

Solution

1. Step 1: Analyze requirements

   The system needs fast reads, flexible data, and can tolerate eventual consistency.

2. Step 2: Match database features to needs

   NoSQL document databases provide flexible schemas, scale horizontally worldwide, and support eventual consistency.

3. Step 3: Evaluate other options

   Relational DBs have strong consistency but less flexible scaling; in-memory stores lack persistence; graph DBs may not scale globally easily.

4. Final Answer:

   NoSQL document database for flexible schema and horizontal scaling -> Option A

5. Quick Check:

   Global scale + flexible data = NoSQL document DB [OK]

Hint: Flexible data + global scale? Pick NoSQL document DB [OK]

Common Mistakes:

• Choosing relational DB despite scaling limits
• Using in-memory store without persistence
• Ignoring horizontal scaling needs