System design interview guide
MakeMyTrip System Design: Flight and Hotel Search
Two courses by the author of this page:
770 lessons · 18 free to read
₹1,111 in India · $35 elsewhere, once
Get System DesignYou own this course
219 lessons · 10 free to read
₹1,333 in India · $35 elsewhere, once
Get Generative AI and Agentic AIYou own this course
Save your progress and get the interview checklist PDF
MakeMyTrip sold $10.39 billion of travel in the year to March 2026. That included $5.83 billion of flights. It also included $2.66 billion of hotels and holiday packages, according to its SEC filing. Almost none of this is its own. The seats belong to airlines. The rooms belong to hotels and suppliers. Each has its own systems and its own speed. Their prices change by the minute. Yet a traveller expects a list of options in about a second. And they expect to pay the price they clicked.
MakeMyTrip is an online travel agency. A traveller searches for flights or hotels, compares them, and books. It looks like search plus booking. But the hard part is where the truth lives. Every seat and every room is in an airline or supplier system. Those systems are slow and cost money to ask. Their answers change all the time. Asking all of them for every search would be too slow and too costly. Showing only saved answers would show prices that no longer exist. So the design is a balance. Save answers so search is fast. Refresh the saved answers smartly so they stay mostly right. Then check the live price again at the moment of booking. That is the moment when being wrong really matters. On top of this sits personal content. One example is showing a user the hotels they looked at recently. MakeMyTrip rebuilt this to respond in tens of milliseconds.
Where it shows up
A natural question for travel and marketplace roles. Think of MakeMyTrip, Goibibo, redBus, Cleartrip, Booking.com, Expedia and Agoda. It is also a common general question. Design a flight search engine. Design a hotel booking system. Design any site that sells things it does not own.
Spec sheetMakeMyTrip
- 01Yearly travel sales
- $10.39 billion (FY26)
- 02Flights
- $5.83 billion (FY26)
- 03Hotels and packages
- $2.66 billion (FY26)
- 04Searches per booking
- many (estimate)
worked through below, with the maths
in this guide
Design MakeMyTrip, part by part
7 parts open to everyone · 3 with a free account · 3 with the course
You can read 7 of 13 parts. A free account opens the deep dive; the course opens all of it.
- Requirementsopen
- Scale estimatesopen
- High-level architectureopen
- Core componentsopen
- Data modelfree account
- Deep dives (5)free account
- Trade-offs to discussfree account
- What the interviewer asks nextwith the course
- The interview scorecardwith the course
- Mock interview on this questionwith the course
- How MakeMyTrip actually does itopen
- Frequently asked questionsopen
- Interview readiness checkopen
The hard parts of this design are taught step by step in the System Design course: Scatter-Gather, Circuit Breaker for Resilience and Search Engines (Elasticsearch, Solr).
Why this question is asked
It tests whether you can design around systems you do not control. Most designs assume your database holds the truth. Here, the truth is in hundreds of outside systems. Every choice trades speed, cost and accuracy. How long can a saved price be trusted? How many suppliers should one search ask? What if the price changes between search and payment? Strong answers keep two paths apart. The read path can be fast and a little wrong. The booking path must be right.
This page is the free part.
The course goes deeper on the MakeMyTrip design
₹1,111 in India$35 everywhere elseonce, for the whole course
The System Design course covers the MakeMyTrip design across a run of lessons, not one page. These 4 alone are about 117 minutes of step-by-step reading, every one with a quiz.
- Cache-Aside Pattern
Cache-aside is said to degrade gracefully when the cache fails. Measured, unwrapped it answered 0.0 percent of requests, and wrapped it answered 13.0, which is exactly the database's capacity.
- Search Engines (Elasticsearch, Solr)
Distributed search engines that power product search, log analysis, and real-time analytics at massive scale.
- Circuit Breaker for Resilience
Stop calling failing services to prevent cascade failures, open, closed, and half-open states.
- Timeout Patterns
Set appropriate timeouts for every external call, deadline propagation and timeout budgets.
all part of
System Design Masterclass
770 lessons · about 290 hours · 18 free to read
₹1,111in India, by UPI
$35everywhere else, by card or PayPal
You own this course
Continue with Cache-Aside Patternpay once,
yours for life
Live from the course bench
Before you design MakeMyTrip, try the questions it rests on.
Real interview questions, live diagrams and measured lab results, pulled at random from the lessons. A new set every time you come back.
Requirements
Always clarify these in the first 5 minutes of the interview. Do not start drawing boxes until both lists are agreed.
Functional requirements
- Search flights by origin, destination, dates and passengers, including flights with a change
- Search hotels by city or area, dates and guests, with filters and sorting
- Show prices, availability and fare or room options, and details for one option
- Check the live price again before payment, and tell the user if it changed
- Book: hold the seat or room with the supplier, take payment and confirm
- Handle cancellations and refunds under each airline's or hotel's rules
- Show personal results, such as hotels the user viewed recently
Non-functional requirements
- Search results in about a second, even though the truth is in slow outside systems
- Keep the number of paid or limited supplier calls under control
- The price shown at payment is the price actually charged
- A slow or failing supplier must not slow down the whole search
- Handle holiday and long-weekend peaks, when many people search the same places
- Never charge a customer without a confirmed booking, and match every booking with the supplier
Back-of-envelope scale estimates
Show your math. Pulling numbers from thin air signals you have not thought about the load.
Yearly travel sales
$10.39 billion (FY26)
This is from MakeMyTrip's SEC filing for the year to 31 March 2026. Travel sales were $10,390.8 million, up 10.4% at fixed exchange rates. This is the value of travel sold, not MakeMyTrip's revenue.
Flights
$5.83 billion (FY26)
Flight sales for the year, the largest part. Flight prices change often. So this is where saved prices go out of date fastest.
Hotels and packages
$2.66 billion (FY26)
Hotel and package sales for the year, up 14.8% at fixed exchange rates. Hotel search is harder to save than it looks. A price depends on dates, number of guests and room mixes.
Searches per booking
many (estimate)
Travellers search, compare and come back several times before booking. Each search can ask many suppliers. This is my estimate: searches outnumber bookings by ten to a hundred times. That is why the read path, not the booking path, drives the cost of the system.
Personal results speed
44 ms typical
In an April 2026 case study with Databricks, MakeMyTrip described its 'recently viewed hotels' feature. Moving it to real-time processing cut the typical delay from about 1.23 seconds to 44 ms. The slowest 1% went from over a minute to about 500 ms.
High-level architecture
Build two paths. The search path is about speed and cost. A search first goes to a store of recent prices and availability. The key is the shape of the search. For flights, it is route and date. For hotels, it is city, dates and guests. Popular searches are almost always answered from this store. For rare searches, or when saved results are too old, the service asks suppliers live. It asks them all at the same time, each with a strict time limit. It returns whatever arrives in time. It does not wait for the slowest supplier. Results are merged, ranked and made personal. Fresh answers are saved for the next search. A background job also refreshes popular routes and cities before users ask. So the busiest searches stay fast and fairly fresh. The booking path is about being right. When the traveller picks an option, the booking service asks that one supplier for the live price. This is called a re-price. If the price changed, the user is told before paying. Then the seat or room is held with the supplier. Payment is taken. The booking is confirmed with the supplier. One booking ID makes every step safe to repeat. Next to both paths runs a real-time personal pipeline. Click events flow through Kafka as they happen. They update each user's data, like the last hotels viewed. The app can read that in milliseconds.
In a real interview, sketch this on the whiteboard before diving into any single box.
Core components
Walk through each service. The interviewer wants to hear what each one owns, not just the names.
Search service and saved results
It answers most searches from a store of recent prices, keyed by the shape of the search. MakeMyTrip's engineers have written about this. Saving results lets them answer repeated requests in a few milliseconds. When a result is missing, they ask the suppliers and save the answer for next time.
Supplier connections
There is one adapter for each airline, booking system or hotel supplier. Each one turns MakeMyTrip's request into that supplier's format. Each has its own time limit, its own call budget and a circuit breaker. Suppliers differ a lot in speed and reliability.
Refreshing saved results
It refreshes prices for popular routes and cities in the background. So the searches most people make are answered fresh from the store. Less popular searches are refreshed only when someone asks. This keeps supplier costs down.
Hotel availability and room choice
It works out which rooms, or mixes of rooms, fit the dates and guests. MakeMyTrip's engineers wrote that many city searches showed low or zero availability. Part of the cause was real peak-season shortage. Part was rates missing in their own system for that number of guests. That is a data problem, not a supply problem.
Re-price and booking
It checks the live price with the one chosen supplier before payment. It holds the seat or room, takes payment and confirms. This is where saved answers get corrected. The traveller sees the real price before they pay.
Real-time personal results
Click events from the apps flow through Kafka into Spark Real-Time Mode. Each user's last viewed hotels are kept in Aerospike. The results are saved in Redis for the app. MakeMyTrip reported a typical delay of 44 ms. Making it real time raised clicks by 7%.
Payments, refunds and matching
It takes payment and handles cancellations under each supplier's rules. Every day it matches every booking against the supplier's records. So a customer is never charged for a booking the supplier did not confirm.
Data model
search_cache. The saved answer to one shape of search. Fast-changing prices, like flights close to departure, are kept for less time. Stable ones are kept longer. The fetched_at time…
Every table for MakeMyTrip, its keys, and which store fits it and why.
Deep dives
Saved prices go out of date. The main problem is that a saved price is a guess. Flight prices can change several times a day. A hotel's last room can sell at any moment. If you save prices for too…
5 deep dives on the parts that break at scale, with 2 diagrams: Saved prices go out of date; Checking the price again at booking; Asking many suppliers without waiting for the slowest.
Trade-offs to discuss
Answer search from saved results versus asking suppliers live. Asking live gives the freshest answer. But it is slow, often limited and sometimes paid per call. It also multiplies with every search. Saved results are fast and cheap…
5 decisions an interviewer expects you to defend, each with the alternative and why it loses here.
What the interviewer asks next
At booking, the re-price is fine and the supplier hold succeeds, but the payment fails. What must happen next?
4 follow-up questions with model answers, the interview scorecard for this question, and a mock interview on Design MakeMyTrip with the AI tutor.
How MakeMyTrip actually does it
The business numbers come from MakeMyTrip's SEC filings for the year to March 2026. The personal results pipeline and its numbers come from an April 2026 Databricks case study, written with MakeMyTrip engineers. The notes on saved results and on hotel availability come from MakeMyTrip's own engineering posts on Medium. We could not read those posts in full. So we use only what their published summaries say. MakeMyTrip has not published the full design of its flight and hotel search. So the rest of the design is a standard one that fits these facts. Estimates are marked as mine.
Lessons to study before this interview
If any of these topics are fuzzy, the interviewer will catch it. Each lesson is 15 to 60 minutes with diagrams, code, and a quiz.
Cache-Aside Pattern
foundation / caching strategies
Search Engines
intermediate / database types storage
Circuit Breaker
advanced / reliability resilience
Timeout Patterns
advanced / reliability resilience
Idempotency Keys
intermediate / api design protocols
Message Queues
intermediate / messaging event systems
Saga Pattern
advanced / distributed systems core
System design interviews at Indian tech companies
28 walkthroughs of the products Indian interviewers ask about, each with the real scale numbers, the architecture and the trade-offs that company had to make.
Food delivery and quick commerce
Payments and fintech
E-commerce
Travel and ticketing
- IRCTC system design
- MakeMyTrip system design (this page)
- BookMyShow system design
- redBus system design
Rides, logistics and services
Streaming and gaming
Frequently asked questions
interview readiness
Are you ready for Design MakeMyTrip?
Three questions from this guide. Answer them without scrolling up, the way you would have to in the room.
Go deeper
This guide is built on these 6 lessons. Each one teaches one piece of the MakeMyTrip design above, step by step.
- Cache-Aside PatternSystem Design · caching strategies · 25 min
- Search Engines (Elasticsearch, Solr)System Design · database types storage · 22 min
- Circuit Breaker for ResilienceSystem Design · reliability resilience · 35 min
- Timeout PatternsSystem Design · reliability resilience · 35 min
- Idempotency KeysSystem Design · api design protocols · 18 min
- Message QueuesSystem Design · messaging event systems · 20 min
Practice with 770 system design lessons
Lifetime access for ₹1,111 in India or $35 elsewhere. Interactive diagrams, quizzes, and 20 capstone projects to practise on.
This one question is not enough for the interview.
Get all 200 questions in the System Design and Distributed Systems pack
Each question has why it is asked, a full answer, what the interviewer listens for, the follow-ups, the common mistakes and a diagram (268 diagrams in all). A PDF you keep, junior to staff level.
Pay by UPI, cards or netbanking through Razorpay. Pay by card or PayPal, in US dollars. Download at once from My packs.
NEWSystem Design Hands-On
Included in the System Design course: real systems, built live
Postgres Sharding: Complete Hands-On (PgBouncer + Citus). 2 h 36 min and 20 chapters: one PostgreSQL loaded until it breaks, then four shards behind a router you write, PgBouncer and Citus, with the 139-page slide deck. The first 15 minutes are free to watch.


