CQRS pattern in Microservices - Architecture Diagram

System Overview - CQRS pattern

The CQRS (Command Query Responsibility Segregation) pattern separates the system into two parts: one for handling commands (writes) and another for handling queries (reads). This helps improve scalability and performance by optimizing each side independently.

Key requirements include handling user requests to update data and fetch data efficiently, while keeping the system consistent and responsive.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  +---------------------+
  |                     |
Command Service     Query Service
  |                     |
  v                     v
Command Database     Query Database (Read-Optimized)
  |
  v
Message Queue
  |
  v
Event Handler
  |
  v
Query Database (Read-Optimized)

Components

User

actor

Initiates commands and queries

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Routes commands and queries to appropriate services

Command Service

service

Handles write operations and updates data

Query Service

service

Handles read operations and returns data

Command Database

database

Stores the authoritative data for writes

Message Queue

message_queue

Asynchronously sends events from Command Service to update Query Database

Event Handler

service

Processes events from the queue to update the Query Database

Query Database (Read-Optimized)

database

Stores data optimized for fast read queries

Request Flow - 12 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Command Service

Command Service → Command Database

Command Service → Message Queue

Message Queue → Event Handler

Event Handler → Query Database (Read-Optimized)

API Gateway → Query Service

Query Service → Query Database (Read-Optimized)

Query Service → API Gateway

API Gateway → Load Balancer

Load Balancer → User

Failure Scenario

Component Fails:Message Queue

Impact:Events about data changes are not delivered to update the Query Database, causing read data to become stale.

Mitigation:Implement message queue replication and retry mechanisms; use monitoring and alerts to detect failures and fallback to direct sync if needed.

Architecture Quiz - 3 Questions

Which component handles write operations in the CQRS pattern?

A API Gateway

B Command Service

C Query Service

D Event Handler

Design Principle

The CQRS pattern separates read and write workloads to optimize performance and scalability. Writes update the authoritative data and asynchronously propagate changes to a read-optimized database, enabling fast queries without impacting write performance.

Practice

1. What is the main purpose of the CQRS pattern in microservices architecture?

easy

A. To separate read and write operations for better scalability

B. To combine all database operations into a single service

C. To encrypt data during transmission between services

D. To cache all data on the client side for faster access

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 side to be optimized and scaled independently, improving performance and maintainability.

3. Final Answer:

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

4. Quick Check:

   CQRS = Separate reads and writes [OK]

Hint: CQRS splits commands and queries separately [OK]

Common Mistakes:

• Thinking CQRS merges all operations into one service
• Confusing CQRS with encryption or caching
• Assuming CQRS only applies to database encryption

2. Which of the following is the correct way to describe the command side in CQRS?

easy

A. Handles read-only queries to fetch data

B. Manages user authentication and sessions

C. Processes write operations that change state

D. Caches data for faster retrieval

Solution

1. Step 1: Define command side role

   The command side in CQRS is responsible for handling commands, which are operations that change the system's state (writes).

2. Step 2: Eliminate incorrect options

   Read-only queries belong to the query side, caching is a separate concern, and authentication is unrelated to CQRS commands.

3. Final Answer:

   Processes write operations that change state -> Option C

4. Quick Check:

   Command side = writes [OK]

Hint: Commands change data, queries read data [OK]

Common Mistakes:

• Confusing command side with query side
• Thinking command side handles caching
• Mixing authentication with CQRS commands

3. Given the following simplified CQRS flow:

1. User sends a command to update an order.
2. Command handler updates the write database.
3. An event is published.
4. The read model updates asynchronously.
What is the main reason for step 4?

medium

A. To validate the command before processing

B. To keep the read database in sync with the write database

C. To rollback the write operation if needed

D. To encrypt the data before sending to the client

Solution

1. Step 1: Understand event role in CQRS

   After the write database updates, an event signals that data changed.

2. Step 2: Purpose of read model update

   The read model updates asynchronously to reflect the latest data for queries, keeping it consistent with writes.

3. Final Answer:

   To keep the read database in sync with the write database -> Option B

4. Quick Check:

   Event updates read model = sync reads [OK]

Hint: Events update read model after writes [OK]

Common Mistakes:

• Thinking event validates or rolls back commands
• Confusing encryption with event handling
• Assuming read model updates happen synchronously

4. In a CQRS system, a developer notices that the read model sometimes shows stale data after a write. What is the most likely cause?

medium

A. The client is caching old data aggressively

B. The command handler failed to update the write database

C. The write database is not replicated properly

D. The event to update the read model is delayed or lost

Solution

1. Step 1: Identify cause of stale read data

   In CQRS, the read model updates asynchronously via events. If events are delayed or lost, the read model lags behind.

2. Step 2: Rule out other causes

   If the write database failed, writes wouldn't succeed. Client caching or replication issues are less likely to cause this specific CQRS symptom.

3. Final Answer:

   The event to update the read model is delayed or lost -> Option D

4. Quick Check:

   Stale reads = delayed event update [OK]

Hint: Stale reads usually mean event delay or loss [OK]

Common Mistakes:

• Blaming write database failure without evidence
• Ignoring event delivery reliability
• Assuming client caching is always the cause

5. You are designing a high-traffic e-commerce system using CQRS. Which approach best handles the challenge of scaling the read side independently from the write side?

hard

A. Use separate databases for read and write models with event-driven synchronization

B. Use a single database for both reads and writes with strong locking

C. Cache all writes on the client and batch update the database later

D. Directly query the write database for all read requests

Solution

1. Step 1: Understand scaling needs in CQRS

   Separating read and write databases allows independent scaling and optimization for each workload.

2. Step 2: Evaluate options for scaling reads

   Event-driven synchronization keeps the read database updated asynchronously, enabling fast, scalable queries without locking.

3. Step 3: Reject unsuitable options

   Single database with locking limits scalability; client caching risks data loss; querying write DB for reads causes contention.

4. Final Answer:

   Use separate databases for read and write models with event-driven synchronization -> Option A

5. Quick Check:

   Separate DBs + events = scalable CQRS [OK]

Hint: Separate read/write DBs with events scale best [OK]

Common Mistakes:

• Using one DB with locking reduces scalability
• Relying on client caching risks consistency
• Reading directly from write DB causes contention