CQRS (Command Query Responsibility Segregation) in HLD - System Design Guide

Problem Statement

When a system uses the same model for both reading and writing data, it often becomes slow and complex. Writes can block reads, and reads can become inefficient because they must handle complex business logic. This leads to poor performance and difficulty scaling as the system grows.

Solution

CQRS separates the system into two parts: one handles commands (writes) and the other handles queries (reads). Each part uses its own model optimized for its task. This separation allows reads and writes to scale independently and simplifies the logic for each operation.

Architecture

Client

↓

Command Model

(Write DB)

↓

Event Store

This diagram shows how client requests split into commands and queries. Commands update the write model and event store, while queries read from a separate read model optimized for fast data retrieval.

Trade-offs

✓ Pros

→

Improves performance by optimizing read and write operations separately.

→

Allows independent scaling of read and write workloads.

→

Simplifies complex business logic by separating command and query responsibilities.

→

Enables use of different data storage technologies for reads and writes.

✗ Cons

→

Increases system complexity due to maintaining two separate models and data stores.

→

Requires eventual consistency between read and write models, which can confuse users.

→

Adds overhead in synchronizing data from write to read models.

Use CQRS when your system has high read and write loads that differ significantly, or when read and write operations require very different data models or performance optimizations.

Avoid CQRS if your system has low traffic (e.g., under 1000 requests per second) or simple data models where the added complexity outweighs the benefits.

Real World Examples

Amazon

Amazon uses CQRS to separate order processing commands from product catalog queries, allowing each to scale and evolve independently.

Netflix

Netflix applies CQRS to handle user actions (commands) separately from content browsing (queries), improving responsiveness and scalability.

Uber

Uber uses CQRS to separate ride request commands from location and pricing queries, enabling efficient real-time updates.

Alternatives

CRUD (Create, Read, Update, Delete)

Uses a single model for both reads and writes without separation.

Use when: Choose CRUD for simple applications with low traffic and straightforward data access patterns.

Event Sourcing

Stores all changes as events and rebuilds state from events, often used together with CQRS but focuses on data storage.

Use when: Choose Event Sourcing when you need full audit trails and the ability to replay state changes.

Summary

CQRS separates the system into command and query parts to optimize performance and scalability.

It allows independent scaling and simpler logic for reads and writes by using different models.

CQRS adds complexity and eventual consistency trade-offs, so it suits systems with distinct read/write needs.

Practice

1. What is the main purpose of using CQRS in system design?

easy

A. To encrypt data for security purposes

B. To combine all database operations into a single service

C. To separate read and write operations for better scalability

D. To reduce the number of servers needed

Solution

1. Step 1: Understand CQRS concept

   CQRS stands for Command Query Responsibility Segregation, which means separating commands (writes) from queries (reads).

2. Step 2: Identify the main benefit

   This separation allows each part to be optimized and scaled independently, improving performance and maintainability.

3. Final Answer:

   To separate read and write operations for better scalability -> Option C

4. Quick Check:

   CQRS = Separate reads and writes [OK]

Hint: CQRS splits commands and queries for scaling [OK]

Common Mistakes:

• Thinking CQRS combines operations into one service
• Confusing CQRS with security encryption
• Assuming CQRS reduces server count directly

2. Which of the following is the correct way to describe the role of the 'Command' in CQRS?

easy

A. It processes write operations that change system state

B. It handles read-only queries to fetch data

C. It stores cached data for faster access

D. It manages user authentication and authorization

Solution

1. Step 1: Define Command role in CQRS

   Commands are responsible for write operations that modify the system's state.

2. Step 2: Differentiate from Query

   Queries only read data without changing it, so they are not commands.

3. Final Answer:

   It processes write operations that change system state -> Option A

4. Quick Check:

   Command = Write operations [OK]

Hint: Commands change data; queries only read [OK]

Common Mistakes:

• Confusing commands with queries
• Thinking commands handle caching
• Assuming commands manage security

3. Consider a system using CQRS where the write side updates a user profile and the read side serves user data. If the write side updates the user's email, what is the expected behavior on the read side immediately after the update?

medium

A. The read side instantly shows the updated email without delay

B. The read side deletes the user data until refreshed

C. The read side rejects the query until the write completes

D. The read side may show the old email briefly due to asynchronous update

Solution

1. Step 1: Understand asynchronous update in CQRS

   In CQRS, the read side is often updated asynchronously via events after the write completes.

2. Step 2: Identify read side behavior after write

   Because of this delay, the read side may temporarily show stale data until it receives the update event.

3. Final Answer:

   The read side may show the old email briefly due to asynchronous update -> Option D

4. Quick Check:

   Read side updates asynchronously = possible stale data [OK]

Hint: Reads update asynchronously, so data may lag briefly [OK]

Common Mistakes:

• Assuming immediate read consistency
• Thinking reads block until writes finish
• Believing read data is deleted during update

4. A developer implemented CQRS but notices that the read model is not updating after commands execute. What is the most likely cause?

medium

A. The read model database is corrupted and cannot be read

B. The command handler is not sending events to update the read model

C. The query side is trying to write data instead of reading

D. The system is using synchronous updates causing deadlocks

Solution

1. Step 1: Identify how read model updates in CQRS

   The read model updates via events sent by the command handler after state changes.

2. Step 2: Diagnose missing updates

   If the read model is not updating, likely the events are not being sent or processed properly.

3. Final Answer:

   The command handler is not sending events to update the read model -> Option B

4. Quick Check:

   Missing events cause read model stale data [OK]

Hint: Check if events are sent after commands [OK]

Common Mistakes:

• Blaming database corruption without evidence
• Confusing query side roles
• Assuming synchronous updates cause deadlocks here

5. You are designing a high-traffic e-commerce system using CQRS. Which approach best ensures that the read side remains highly available and scalable while keeping data reasonably fresh?

hard

A. Use event sourcing to asynchronously update read models and deploy multiple read replicas

B. Use a single database for both reads and writes to avoid data duplication

C. Synchronously update the read model within the command transaction to ensure consistency

D. Disable caching on the read side to always fetch fresh data from the write database

Solution

1. Step 1: Understand scalability needs in CQRS

   Separating reads and writes allows scaling read replicas independently to handle high traffic.

2. Step 2: Use event sourcing for asynchronous updates

   Event sourcing helps keep read models updated asynchronously, balancing freshness and availability.

3. Step 3: Evaluate other options

   Single database limits scalability; synchronous updates reduce availability; disabling caching hurts performance.

4. Final Answer:

   Use event sourcing to asynchronously update read models and deploy multiple read replicas -> Option A

5. Quick Check:

   Event sourcing + read replicas = scalable, fresh reads [OK]

Hint: Event sourcing + replicas = scalable reads with freshness [OK]

Common Mistakes:

• Using single DB limits scalability
• Synchronous updates reduce availability
• Disabling cache hurts performance