Preparing chapter
Loading your data design lesson
The curriculum shell is ready while the requested chapter is being prepared. You can wait here or return to the design library.
Preparing chapter
The curriculum shell is ready while the requested chapter is being prepared. You can wait here or return to the design library.
BookMyShow · Data Engineering · Defend the trade-offs
Practice 40 questions across requirements, correctness, contracts, streaming, lakehouse, governance, recovery, and scale.
40-question interview workspace
Eight rounds cover the complete BookMyShow big-data design.
QUESTION 01 / 40
Requirements + sizingComprehensive interview answer
Seat ownership, hold expiry, booking confirmation, and payment state transitions require synchronous authority. Risk signals, operations, product analytics, and settlement use explicit second, minute, hourly, or T+1 freshness. Making every consumer synchronous would couple booking availability to the whole data platform; allowing every path to lag would make seat and money decisions unsafe.
Map every consumer to its source of truth, freshness SLO, stale fallback, and failure behavior before choosing tools.
Five-minute whiteboard
Move from the customer promise to scale, transaction truth, data flow, analytics, and recovery. Select any step to see exactly what to draw and explain.
Add to the diagram
Place Customer → BookMyShow edge → Booking domain across the top. Write the two invariants beside it: one active owner per show-seat and every payment movement traceable to a booking.
Explain the decision
Separate the customer-facing booking path from downstream data products. Seat ownership and payment transitions need synchronous authority; search analytics, occupancy, fraud features, and settlement can use declared freshness windows.
The interviewer should know what must never be wrong before tools appear.
