Why Message delivery guarantees in HLD? - Purpose & Use Cases

The Big Idea

What if your messages got lost or duplicated without you knowing?

The Scenario

Imagine sending important letters by hand to your friends across town. You write the letter, but you have no way to know if your friend received it, if it got lost, or if they read it twice. You must keep track of every letter yourself, hoping none get lost or duplicated.

The Problem

Manually tracking message delivery is slow and unreliable. You can lose messages, send duplicates, or miss confirmations. This causes confusion, errors, and wasted time fixing problems. Without guarantees, you can't trust that your messages reach their destination exactly once.

The Solution

Message delivery guarantees automate tracking and ensure messages arrive safely. They provide clear rules like "at least once," "at most once," or "exactly once" delivery. This removes guesswork, prevents lost or duplicate messages, and builds trust in communication between systems.

Before vs After

✗ Before

sendMessage(msg)
// no confirmation, no retry, no tracking

✓ After

sendMessageWithGuarantee(msg, deliveryType="exactly_once")
// automatic retry, confirmation, and deduplication

What It Enables

It enables reliable, fault-tolerant communication where systems can trust messages are delivered correctly and only once.

Real Life Example

Online shopping platforms use message delivery guarantees to ensure your order confirmation is sent exactly once, avoiding duplicate charges or missed orders.

Key Takeaways

Manual message sending risks loss and duplication.

Delivery guarantees automate safe, reliable message handling.

This builds trust and consistency in distributed systems.

Practice

1. Which message delivery guarantee ensures that a message is never delivered more than once, but some messages might be lost?

easy

A. Exactly once

B. At most once

C. At least once

D. None of the above

Solution

1. Step 1: Understand 'At most once' guarantee

   This guarantee means messages can be lost but never duplicated.

2. Step 2: Compare with other guarantees

   'At least once' may duplicate messages, 'Exactly once' avoids loss and duplication but is complex.

3. Final Answer:

   At most once -> Option B

4. Quick Check:

   At most once = no duplicates, possible loss [OK]

Hint: No duplicates but possible loss means 'At most once' [OK]

Common Mistakes:

• Confusing 'At most once' with 'At least once'
• Thinking 'Exactly once' is simple
• Assuming 'At most once' never loses messages

2. Which of the following is the correct description of the 'Exactly once' message delivery guarantee?

easy

A. Messages are delivered once without loss or duplication

B. Messages may be lost but never duplicated

C. Messages may be duplicated but never lost

D. Messages are delivered at least once, possibly duplicated

Solution

1. Step 1: Define 'Exactly once' guarantee

   This guarantee ensures each message is delivered once, no loss, no duplication.

2. Step 2: Eliminate other options

   'Messages may be lost but never duplicated' is 'At most once', 'Messages may be duplicated but never lost' and 'delivered at least once, possibly duplicated' describe 'At least once'.

3. Final Answer:

   Messages are delivered once without loss or duplication -> Option A

4. Quick Check:

   Exactly once = no loss, no duplicates [OK]

Hint: Exactly once means no loss and no duplicates [OK]

Common Mistakes:

• Mixing 'Exactly once' with 'At least once'
• Believing 'Exactly once' allows duplicates
• Confusing 'At most once' with 'Exactly once'

3. Consider a message queue system that uses 'At least once' delivery. If a message is sent and the receiver crashes before acknowledging, what is the likely outcome?

medium

A. The message is lost and never delivered

B. The message is delivered once without duplication

C. The message is delivered at most once

D. The message may be delivered multiple times

Solution

1. Step 1: Understand 'At least once' behavior on receiver crash

   If receiver crashes before ack, sender retries, causing possible duplicates.

2. Step 2: Analyze options

   The message is not lost but sender retries on no ack, so may be delivered multiple times to ensure at least once.

3. Final Answer:

   The message may be delivered multiple times -> Option D

4. Quick Check:

   At least once = possible duplicates [OK]

Hint: Receiver crash before ack causes duplicates in 'At least once' [OK]

Common Mistakes:

• Assuming message is lost on crash
• Confusing 'At least once' with 'At most once'
• Ignoring possibility of duplicates

4. A system claims to provide 'Exactly once' delivery but sometimes messages are duplicated. What is the most likely cause?

medium

A. The system uses 'At least once' delivery without deduplication

B. The system uses 'At most once' delivery internally

C. The system does not handle acknowledgments properly

D. The system drops messages on network failure

Solution

1. Step 1: Identify cause of duplicates in 'Exactly once'

   Duplicates usually happen if 'At least once' is used without deduplication.

2. Step 2: Evaluate other options

   'At most once' causes losses not duplicates, improper ack handling or dropping messages cause losses or retries but exactly once needs deduplication atop at least once.

3. Final Answer:

   The system uses 'At least once' delivery without deduplication -> Option A

4. Quick Check:

   Duplicates mean missing deduplication in 'At least once' [OK]

Hint: Duplicates in 'Exactly once' mean missing deduplication [OK]

Common Mistakes:

• Assuming 'At most once' causes duplicates
• Ignoring deduplication step
• Confusing message loss with duplication

5. You are designing a payment processing system that must never lose or duplicate transactions. Which message delivery guarantee should you choose and why?

hard

A. At most once, because it avoids duplicates

B. At least once, because it ensures no message loss

C. Exactly once, because it guarantees no loss and no duplicates

D. None, because message delivery guarantees are not relevant

Solution

1. Step 1: Identify system requirements

   Payment processing must avoid losing or duplicating transactions.

2. Step 2: Match guarantee to requirements

   'Exactly once' ensures messages are delivered once without loss or duplication, fitting the need.

3. Final Answer:

   Exactly once, because it guarantees no loss and no duplicates -> Option C

4. Quick Check:

   Payment systems need exactly once delivery [OK]

Hint: No loss or duplicates means choose 'Exactly once' [OK]

Common Mistakes:

• Choosing 'At most once' and risking loss
• Choosing 'At least once' and risking duplicates
• Ignoring delivery guarantees in critical systems