Why booking tests availability and concurrency in LLD - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is concurrency control important in booking systems?

Imagine a popular online booking system where many users try to book the same slot simultaneously. Why is concurrency control crucial in this scenario?

A To prevent race conditions that could lead to double booking of the same slot.

B To allow users to book slots even if they are already taken, increasing sales.

C To slow down the booking process so users wait longer and reduce server load.

D To ensure that multiple users can book the same slot at the same time without any restrictions.

💡 Hint

Think about what happens if two people book the same slot at the exact same time.

Concurrency control prevents race conditions where two or more users might book the same slot simultaneously, causing double booking and inconsistent data.

❓ Architecture

intermediate

Which component is essential to handle availability in a booking system?

In a booking system, which component is primarily responsible for managing the availability of slots and preventing conflicts?

A Database with locking or transactional support to manage slot availability.

B User Interface that shows available slots.

C Notification service to alert users about bookings.

D Logging service to record booking attempts.

💡 Hint

Think about where the actual data about slot availability is stored and controlled.

The database manages slot availability using locks or transactions to ensure that no two bookings can reserve the same slot simultaneously.

❓ scaling

advanced

How to scale a booking system to handle high concurrency without losing availability accuracy?

You need to design a booking system that can handle thousands of concurrent booking requests per second without double booking. Which approach best supports this requirement?

A Allow eventual consistency and resolve conflicts manually after bookings are made.

B Use a single database instance with no caching and rely on simple queries.

C Implement distributed locking or use a centralized coordination service like ZooKeeper to manage slot locks.

D Disable concurrency controls to improve speed and fix errors later.

💡 Hint

Think about how to coordinate access to shared resources across many servers.

Distributed locking or centralized coordination ensures that concurrent requests are serialized properly, preventing double bookings even at scale.

❓ tradeoff

advanced

What is the tradeoff when using pessimistic locking for booking availability?

Pessimistic locking locks a slot during booking to prevent others from booking it simultaneously. What is a key tradeoff of this approach?

A It improves system throughput by allowing many users to book simultaneously.

B It allows users to book slots even if they are already locked.

C It eliminates the need for any database transactions.

D It can cause delays or reduced system responsiveness due to waiting for locks to release.

💡 Hint

Consider what happens when many users try to book the same slot and have to wait.

Pessimistic locking prevents conflicts but can reduce responsiveness because users must wait for locks to be released before proceeding.

❓ estimation

expert

Estimate the maximum concurrent booking requests a system can handle with optimistic concurrency control

A booking system uses optimistic concurrency control with version checks on each slot record. If the system can process 500 booking requests per second and the average retry rate due to conflicts is 20%, what is the maximum number of concurrent booking requests the system can handle without significant delays?

A Exactly 500 concurrent requests, since retries do not affect throughput.

B Approximately 400 concurrent requests, accounting for retries.

C More than 600 concurrent requests, because retries improve throughput.

D Less than 300 concurrent requests, due to high retry overhead.

💡 Hint

Calculate effective throughput after accounting for retries.

With 20% retries, effective throughput is 500 / 1.2 ≈ 416 requests per second, so max concurrency is about 400 requests.

Practice

1. Why is it important to handle concurrency when booking test slots in a system?

easy

A. To allow unlimited bookings for the same slot

B. To slow down the booking process intentionally

C. To prevent multiple users from booking the same slot at the same time

D. To avoid showing available slots to users

Solution

1. Step 1: Understand concurrency in booking

   Concurrency means multiple users try to book the same slot simultaneously.

2. Step 2: Identify the problem caused by concurrency

   If concurrency is not handled, multiple users can book the same slot, causing double bookings.

3. Final Answer:

   To prevent multiple users from booking the same slot at the same time -> Option C

4. Quick Check:

   Concurrency handling = prevent double bookings [OK]

Hint: Concurrency means multiple users booking simultaneously [OK]

Common Mistakes:

• Thinking concurrency allows unlimited bookings
• Ignoring the need to prevent double bookings
• Assuming concurrency slows down the system intentionally

2. Which of the following is a correct way to ensure availability checks during booking in a system?

easy

A. Check slot availability after booking confirmation

B. Lock the slot before confirming the booking

C. Allow booking without checking availability

D. Ignore concurrency and rely on user honesty

Solution

1. Step 1: Understand locking in booking systems

   Locking a slot means reserving it temporarily to prevent others from booking it simultaneously.

2. Step 2: Identify when to check availability

   Availability must be checked and locked before confirming booking to avoid conflicts.

3. Final Answer:

   Lock the slot before confirming the booking -> Option B

4. Quick Check:

   Lock before confirm = correct availability check [OK]

Hint: Lock slot before booking to avoid conflicts [OK]

Common Mistakes:

• Checking availability after booking causes errors
• Ignoring availability checks leads to double bookings
• Relying on user honesty is not a system design

3. Consider this simplified booking flow code snippet:

def book_slot(slot_id):
    if is_available(slot_id):
        reserve(slot_id)
        confirm_booking(slot_id)
        return 'Booked'
    else:
        return 'Unavailable'

What issue can arise if two users call book_slot at the same time for the same slot_id?

medium

A. Both users might get 'Booked' causing double booking

B. The system crashes due to race condition

C. Both users get 'Unavailable' response

D. Only one user can call the function at a time automatically

Solution

1. Step 1: Analyze the code flow for concurrency

   Both users check availability before reservation without locking, so both may see the slot as available.

2. Step 2: Understand race condition effect

   Without locking, both reserve and confirm booking, causing double booking.

3. Final Answer:

   Both users might get 'Booked' causing double booking -> Option A

4. Quick Check:

   Race condition = double booking risk [OK]

Hint: Check-then-act without lock causes double booking [OK]

Common Mistakes:

• Assuming system crashes automatically
• Thinking both get 'Unavailable' response
• Believing function serializes calls automatically

4. In a booking system, the code uses a simple availability check without locking:

if check_availability(slot):
    book(slot)

Users report double bookings. What is the best fix?

medium

A. Add a lock or transaction around availability check and booking

B. Remove availability check to speed up booking

C. Increase server hardware to handle more requests

D. Notify users to book slower

Solution

1. Step 1: Identify the cause of double bookings

   Without locking, multiple users can pass availability check simultaneously causing conflicts.

2. Step 2: Apply concurrency control

   Using locks or transactions ensures only one booking proceeds at a time for the same slot.

3. Final Answer:

   Add a lock or transaction around availability check and booking -> Option A

4. Quick Check:

   Locking fixes concurrency issues [OK]

Hint: Use locks or transactions to fix concurrency bugs [OK]

Common Mistakes:

• Removing availability check causes more errors
• Upgrading hardware does not fix concurrency logic
• Telling users to slow down is not a system fix

5. You are designing a test booking system that must handle thousands of users booking slots concurrently. Which design approach best ensures availability and prevents double bookings?

hard

A. Show all slots as available and accept bookings first come, first served

B. Allow users to book without checks and fix conflicts later manually

C. Use a single global lock for all bookings to serialize requests

D. Use optimistic locking with retries and real-time slot availability updates

Solution

1. Step 1: Understand scalability needs

   Thousands of users require a scalable approach that avoids bottlenecks.

2. Step 2: Evaluate locking strategies

   Single global lock serializes all requests causing delays; manual fixes cause poor user experience.

3. Step 3: Choose optimistic locking with retries

   This approach allows concurrent attempts, detects conflicts, retries, and updates availability promptly.

4. Final Answer:

   Use optimistic locking with retries and real-time slot availability updates -> Option D

5. Quick Check:

   Optimistic locking + updates = scalable concurrency [OK]

Hint: Optimistic locking scales better than global locks [OK]

Common Mistakes:

• Using global lock causes slow system
• Ignoring concurrency leads to double bookings
• Manual conflict fixes harm user experience