2
showcase
Shipped: The data model, explained
Documented the data model in README.md: each table's purpose and
relationships, each constraint (foreign keys, the UNIQUE on
reservations.seat_id, the composite index) named alongside what it
prevents, and the query plan for the highest-traffic query (SCAN vs
SEARCH USING COVERING INDEX).
Also ran the exact same query at 10x scale (100,000 seats vs 10,000) to
find what actually breaks first -- not the index (it keeps using SEARCH),
but the missing pagination: response time went from 0.662ms/666 rows to
5.681ms/6,666 rows and 272KB, growing linearly with result size. The
decision documented: add LIMIT/OFFSET before that becomes a real problem.
Repository: https://github.com/GhulamMustafaAnsari/ticket-sales
Live: https://ticket-sales.bonto.run/events/1/seats?status=free
Built for the Verified Backend Internship · Documentation
Add a comment
0/2000