Why Reservation and hold system in LLD? - Purpose & Use Cases

The Big Idea

What if your system could stop double bookings and lost sales instantly?

The Scenario

Imagine you run a small event ticket booth where customers call or come in person to reserve seats. You write down each reservation on paper or a simple spreadsheet. When many customers call at once, you struggle to keep track of who reserved what, and double bookings happen often.

The Problem

Manually tracking reservations is slow and confusing. You can easily lose track of which seats are held or sold. Mistakes cause unhappy customers and lost sales. It's hard to update availability in real-time, especially when many people try to book simultaneously.

The Solution

A reservation and hold system automates seat holding and booking. It temporarily blocks seats for a customer while they decide, preventing others from booking the same seat. The system updates availability instantly and handles many users at once without errors.

Before vs After

✗ Before

Check seat availability in spreadsheet
If free, mark as reserved
Wait for customer confirmation
If no confirmation, manually free seat

✓ After

Hold seat with expiration timer
If customer confirms, finalize booking
If timer expires, release seat automatically

What It Enables

This system makes booking fast, reliable, and fair, allowing many customers to reserve seats simultaneously without conflicts.

Real Life Example

Online movie ticket platforms use reservation and hold systems to let you pick seats and hold them briefly while you pay, ensuring no double bookings happen.

Key Takeaways

Manual reservation is error-prone and slow.

Reservation and hold systems automate seat blocking and release.

They enable smooth, real-time booking for many users.

Practice

1. What is the primary purpose of a hold in a reservation and hold system?

easy

A. To delete all reservations from the system

B. To permanently reserve a resource without expiration

C. To cancel a confirmed reservation immediately

D. To temporarily block a resource before final booking

Solution

1. Step 1: Understand the role of a hold

   A hold temporarily blocks a resource to prevent others from booking it while the user decides.

2. Step 2: Differentiate hold from reservation

   A reservation is permanent until canceled, while a hold expires if not confirmed.

3. Final Answer:

   To temporarily block a resource before final booking -> Option D

4. Quick Check:

   Hold = Temporary block [OK]

Hint: Holds are temporary blocks, not permanent reservations [OK]

Common Mistakes:

• Confusing hold with permanent reservation
• Thinking holds never expire
• Assuming holds cancel reservations

2. Which data structure is best suited to track holds with expiration times efficiently?

easy

A. Simple array without ordering

B. Linked list without timestamps

C. Hash map with timestamps and a priority queue for expirations

D. Stack data structure

Solution

1. Step 1: Identify requirements for hold tracking

   We need fast lookup by hold ID and efficient expiration handling.

2. Step 2: Choose data structures

   A hash map allows quick hold lookup; a priority queue orders holds by expiration for timely removal.

3. Final Answer:

   Hash map with timestamps and a priority queue for expirations -> Option C

4. Quick Check:

   Hash map + priority queue = efficient hold tracking [OK]

Hint: Use hash map for lookup and priority queue for expirations [OK]

Common Mistakes:

• Using unordered arrays causing slow expiration checks
• Choosing stack which is LIFO, not suitable for expirations
• Ignoring timestamps in data structure

3. Consider this pseudo-code for confirming a hold:

if hold.exists(hold_id) and not hold.is_expired(hold_id):
    reservation.create(hold.resource)
    hold.remove(hold_id)
    return "Confirmed"
else:
    return "Failed"

What will be the output if the hold has expired?

medium

A. "Failed"

B. "Confirmed"

C. Error due to missing hold

D. "Confirmed" but resource is double booked

Solution

1. Step 1: Check hold existence and expiration

   The code confirms only if hold exists and is not expired.

2. Step 2: Analyze expired hold case

   If hold is expired, condition fails and returns "Failed" without creating reservation.

3. Final Answer:

   "Failed" -> Option A

4. Quick Check:

   Expired hold = "Failed" confirmation [OK]

Hint: Expired holds cause confirmation to fail [OK]

Common Mistakes:

• Assuming expired holds confirm successfully
• Expecting errors instead of failure message
• Ignoring hold expiration check

4. A developer wrote this code to release expired holds:

for hold in holds:
    if hold.expiration_time < current_time:
        holds.remove(hold)

What is the main issue with this code?

medium

A. Holds should not be removed, only marked expired

B. Modifying a list while iterating causes skipped elements or errors

C. Expiration time comparison is incorrect

D. Loop should use while instead of for

Solution

1. Step 1: Understand iteration and modification

   Removing items from a list while iterating over it causes skipping or runtime errors.

2. Step 2: Identify correct approach

   Use a separate list to collect expired holds or iterate over a copy to safely remove.

3. Final Answer:

   Modifying a list while iterating causes skipped elements or errors -> Option B

4. Quick Check:

   Remove during iteration = skipped elements [OK]

Hint: Never remove items from list while looping over it [OK]

Common Mistakes:

• Ignoring iteration modification side effects
• Assuming expiration comparison is wrong
• Thinking loop type causes the issue

5. You need to design a scalable reservation and hold system for a popular event with thousands of simultaneous users. Which approach best ensures no double booking and timely hold expiration?

hard

A. Use distributed locks on resources, store holds with TTL in a distributed cache, and confirm with atomic transactions

B. Store all holds in a single database table without expiration, confirm by updating status

C. Allow multiple holds per resource and resolve conflicts manually later

D. Use client-side timers to expire holds and update server asynchronously

Solution

1. Step 1: Prevent double booking with distributed locks

   Distributed locks ensure only one user can hold a resource at a time across servers.

2. Step 2: Use TTL in distributed cache for hold expiration

   TTL automatically expires holds after timeout, preventing indefinite blocking.

3. Step 3: Confirm holds atomically

   Atomic transactions guarantee reservation creation without race conditions.

4. Final Answer:

   Use distributed locks on resources, store holds with TTL in a distributed cache, and confirm with atomic transactions -> Option A

5. Quick Check:

   Distributed locks + TTL + atomic confirm = scalable, safe system [OK]

Hint: Combine distributed locks, TTL cache, and atomic confirm for scale [OK]

Common Mistakes:

• Ignoring concurrency causing double booking
• Relying on client-side expiration only
• Not using atomic operations for confirmation