One-to-one messaging in HLD - System Design Guide

Problem Statement

When two users want to exchange messages directly, a naive system can cause message loss, delays, or inconsistent message order. Without a dedicated mechanism, messages may not be delivered reliably or in the correct sequence, leading to poor user experience and confusion.

Solution

One-to-one messaging systems ensure that messages between two users are delivered reliably and in order by maintaining a dedicated communication channel or session. The system stores messages persistently, manages delivery acknowledgments, and orders messages before presenting them to users, ensuring a seamless and consistent conversation flow.

Architecture

User A

(Sender)

→Messaging

↓

User B

(Sender)

This diagram shows two users exchanging messages through a messaging server that stores and forwards messages to ensure reliable and ordered delivery.

Trade-offs

✓ Pros

→

Ensures reliable delivery of messages even if the receiver is offline.

→

Maintains message order for a coherent conversation experience.

→

Supports message persistence for history and synchronization across devices.

→

Enables real-time or near-real-time communication.

✗ Cons

→

Requires server-side storage and management, increasing infrastructure complexity.

→

Needs mechanisms for handling offline users and message retries.

→

Scaling to millions of users requires careful design to avoid bottlenecks.

Use when building chat applications or systems where direct, reliable, and ordered communication between two users is required, especially at scales above thousands of concurrent users.

Avoid if the system only requires simple notifications or one-way messaging without strict ordering or reliability guarantees, or if the user base is very small (under 100 concurrent users) where simpler methods suffice.

Real World Examples

WhatsApp

Uses one-to-one messaging with end-to-end encryption to ensure reliable, ordered delivery of messages between users even when offline.

Facebook Messenger

Implements one-to-one messaging with message storage and delivery receipts to provide seamless chat experiences across devices.

Slack

Supports direct messages between users with message persistence and ordering to maintain conversation context.

Alternatives

Broadcast Messaging

Sends messages to multiple recipients simultaneously rather than a single user.

Use when: Use when messages need to be sent to groups or all users, not just one-to-one.

One-way Notification

Delivers messages without expecting replies or maintaining conversation state.

Use when: Use for alerts or notifications where message ordering and persistence are less critical.

Summary

One-to-one messaging systems prevent message loss and disorder by managing delivery through a server.

They store messages persistently and ensure ordered delivery even if users are offline.

This pattern is essential for reliable, real-time chat applications between two users.