Why messaging requires real-time architecture in HLD - Architecture Impact

System Overview - Why messaging requires real-time architecture

This system enables instant message delivery between users. It must handle many users sending and receiving messages quickly and reliably. The key requirement is low delay so conversations feel natural and real-time.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  v
Message Service <-> Message Queue <-> Notification Service
  |                              |
  v                              v
Database                      Cache

Components

User

client

Sends and receives messages in real-time

Load Balancer

load_balancer

Distributes incoming user requests evenly to backend servers

API Gateway

api_gateway

Handles client requests, authentication, and routes to services

Message Service

service

Processes sending and receiving messages, interacts with queue and database

Message Queue

message_queue

Buffers messages for asynchronous processing and delivery

Notification Service

service

Sends real-time notifications to users about new messages

Database

database

Stores message history and user data

Cache

cache

Stores recent messages for fast retrieval

Request Flow - 8 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Message Service

Message Service → Message Queue

Message Queue → Notification Service

Notification Service → User

Message Service → Database

Message Service → Cache

Failure Scenario

Component Fails:Message Queue

Impact:Messages cannot be buffered for delivery, causing delays or loss of real-time notifications

Mitigation:Use replicated queues and fallback to direct delivery attempts; alert operators to fix queue issues quickly

Architecture Quiz - 3 Questions

Why is the Message Queue important in this real-time messaging system?

A It stores user profiles permanently

B It buffers messages to ensure smooth and ordered delivery

C It balances load between users

D It authenticates user requests

Design Principle

This architecture uses asynchronous messaging with a queue to handle real-time message delivery reliably and at scale. Caching recent messages reduces database load and improves response speed. Load balancing and API gateway ensure scalability and security. The design balances speed, reliability, and user experience.

Practice

1. Why is real-time architecture important for messaging systems?

easy

A. It delivers messages instantly for smooth conversations.

B. It stores messages for long-term archival only.

C. It processes messages in batches once a day.

D. It encrypts messages without sending them.

Solution

1. Step 1: Understand messaging user experience

   Users expect messages to appear immediately during chats for natural flow.

2. Step 2: Connect real-time architecture to instant delivery

   Real-time systems use open connections to send messages instantly without delay.

3. Final Answer:

   It delivers messages instantly for smooth conversations. -> Option A

4. Quick Check:

   Instant delivery = Real-time architecture [OK]

Hint: Real-time means instant message delivery [OK]

Common Mistakes:

• Confusing real-time with batch processing
• Thinking real-time only means encryption
• Assuming real-time stores messages only

2. Which technology is commonly used to maintain open connections for real-time messaging?

easy

A. WebSockets for continuous connection

B. FTP for file transfers

C. HTTP polling every hour

D. SMTP for email delivery

Solution

1. Step 1: Identify open connection methods

   Real-time messaging needs a persistent connection to avoid delays.

2. Step 2: Match technology to persistent connection

   WebSockets keep a continuous open connection, unlike HTTP polling or FTP.

3. Final Answer:

   WebSockets for continuous connection -> Option A

4. Quick Check:

   Open connection = WebSockets [OK]

Hint: WebSockets keep connections open for real-time [OK]

Common Mistakes:

• Choosing HTTP polling which is slow
• Confusing FTP or SMTP with messaging protocols
• Thinking email protocols support real-time chat

3. Consider a messaging system using WebSockets. What happens if the server delays message delivery by 5 seconds?

medium

A. Messages are delivered in batches every minute.

B. Users see messages instantly without delay.

C. Messages get lost and never arrive.

D. Messages appear late, causing poor chat experience.

Solution

1. Step 1: Understand WebSocket behavior

   WebSockets deliver messages instantly if server sends immediately.

2. Step 2: Analyze impact of 5-second delay

   If server delays sending, users see messages late, hurting chat flow.

3. Final Answer:

   Messages appear late, causing poor chat experience. -> Option D

4. Quick Check:

   Server delay = Late messages [OK]

Hint: Server delay causes late message display [OK]

Common Mistakes:

• Assuming WebSockets fix server delays
• Thinking messages get lost due to delay
• Confusing batch delivery with real-time

4. A messaging system uses WebSockets but users report delayed messages. What is the most likely cause?

medium

A. WebSocket protocol does not support real-time.

B. Server processes messages slowly before sending.

C. Clients do not support HTML5.

D. Messages are encrypted end-to-end.

Solution

1. Step 1: Check WebSocket capabilities

   WebSockets support real-time delivery if server sends promptly.

2. Step 2: Identify delay source

   Slow server processing before sending causes message delays, not WebSocket itself.

3. Final Answer:

   Server processes messages slowly before sending. -> Option B

4. Quick Check:

   Slow server = Delayed messages [OK]

Hint: Delays usually come from server processing, not WebSocket [OK]

Common Mistakes:

• Blaming WebSocket protocol for delays
• Assuming client HTML5 support causes delay
• Confusing encryption with delivery speed

5. You design a messaging app for millions of users. Which real-time architecture choice best supports fast, reliable message delivery at scale?

hard

A. Store messages locally on user devices only.

B. Send messages via email every hour.

C. Use WebSockets with load balancers and message queues.

D. Use HTTP polling every 10 minutes.

Solution

1. Step 1: Identify scalable real-time components

   WebSockets provide instant delivery; load balancers distribute traffic; queues ensure reliability.

2. Step 2: Compare other options for scale and speed

   Email and polling are slow; local storage alone can't deliver messages to others.

3. Final Answer:

   Use WebSockets with load balancers and message queues. -> Option C

4. Quick Check:

   Scalable real-time = WebSockets + load balancers + queues [OK]

Hint: Combine WebSockets, load balancers, and queues for scale [OK]

Common Mistakes:

• Choosing slow batch methods for real-time needs
• Ignoring load balancing for millions of users
• Relying only on local device storage