This is a BAD example of how you should do a SD interview. No matter how deep you understand how the system work, always start with high level disign and then dive deep. Especially when the interviwer ask you to do so. I am pretty sure the EM candidate in the video has a lot of expierence on this kind of topic, but I think the way he keep talking himself and ignored what the interview told him to do is definitely a red flag for any company's interview.
Its good to remind that the interviewee should be always asking and confirming with the interviewer about the decisions and next steps. You will probably get a better result if you use the interviewer as a partner in the system design.
Great episode! I loved seeing how an EM took his time to really dive deep into subjects. It felt like if the interviewer didn't rush him he would've given us a 5h masterclass haha
It is Informative. I wish there were discussions around how the hotel search will work on geo locations and how the data will be partitioned (sharded).
He mentioned that there is an 18TB database but he didn't talk that there would be huge performance issues with that. Also, the inventory table approach is sorta strange - will he populate all the inventories for 10 years forward?
By assigning room numbers at check in instead of at booking, how do you guarantee that customers will be able to have a particular room for their entire stay?
Great approach - Liked the way he jotted down the functional & non functional requirements through mind map. Just my opinion, the 5 room types are across the 1 M Hotels, shouldn't be 5M room types. The types remain same so that we can store the room types in enum.
For the deadlock, a better way would be to provide API to the reservations API which would only be released once the hold on the room is released or that reservation is cancelled. This would prevent double booking using the reservations API as an argument would be the roomType and status of the room. I think the way it is explained in the video with constraints and other Sql statements needs a revisit.
I got a question: How do you maintain referential integrity across the 2 databases? I'm assuming one database would contain the Hotel table and the other the Inventory and Reservation table, the latter referencing hotel_id in the former.
Hm, I don't feel the candidate was confident enough in his proposals. Swinging from one side to another without actually answering interviewer's questions
Should have gone deeper into Kafka and how orders are managed. Also, one of the biggest thing with hotels is location so he should have gone into that as well.
I won't go for BFF, To solve under fetching and over fetching issue, graphql is much better option instead of building out BFF for each UI. Too much overhead cost and even complicates the system.
Make sure you're interview-ready with Exponent's system design interview prep course: bit.ly/42Wsa3x
This is a BAD example of how you should do a SD interview. No matter how deep you understand how the system work, always start with high level disign and then dive deep. Especially when the interviwer ask you to do so. I am pretty sure the EM candidate in the video has a lot of expierence on this kind of topic, but I think the way he keep talking himself and ignored what the interview told him to do is definitely a red flag for any company's interview.
Interviewer : Let's quickly go through the High Level Design of the major flows.
Interviewee: Yes, builds a block and starts writing SQL queries
Its good to remind that the interviewee should be always asking and confirming with the interviewer about the decisions and next steps. You will probably get a better result if you use the interviewer as a partner in the system design.
Great episode! I loved seeing how an EM took his time to really dive deep into subjects. It felt like if the interviewer didn't rush him he would've given us a 5h masterclass haha
The tool is Whimsical.
Do we need to write code in EM roles , I mean is dSA required in EM interviews?
It is Informative. I wish there were discussions around how the hotel search will work on geo locations and how the data will be partitioned (sharded).
He mentioned that there is an 18TB database but he didn't talk that there would be huge performance issues with that. Also, the inventory table approach is sorta strange - will he populate all the inventories for 10 years forward?
What tool is being used here? This is awesome!!😊
By assigning room numbers at check in instead of at booking, how do you guarantee that customers will be able to have a particular room for their entire stay?
Great approach - Liked the way he jotted down the functional & non functional requirements through mind map. Just my opinion, the 5 room types are across the 1 M Hotels, shouldn't be 5M room types. The types remain same so that we can store the room types in enum.
For the deadlock, a better way would be to provide API to the reservations API which would only be released once the hold on the room is released or that reservation is cancelled. This would prevent double booking using the reservations API as an argument would be the roomType and status of the room. I think the way it is explained in the video with constraints and other Sql statements needs a revisit.
I got a question: How do you maintain referential integrity across the 2 databases? I'm assuming one database would contain the Hotel table and the other the Inventory and Reservation table, the latter referencing hotel_id in the former.
Hm, I don't feel the candidate was confident enough in his proposals. Swinging from one side to another without actually answering interviewer's questions
Important topic to cover here: payment failures.
Was he hired? Or not
Nice session. Which tool are you using to draw?
Hi AmiTech, the tool being used here for drawing is called Whimsical!
Very Nice, thanks for sharing!
What about searching of hotels? Should not be using elastic search which is search database that can be optimisation
@exponent plz let us know the tool he used!!
Hi Mansi! The whiteboard tool he is using is called Whimsical
I'm curious what this whiteboard tool is.
Hey myrondai! The whiteboard tool is "Whimsical"!
@@tryexponent thank you!
Which platform you are using for system design while mock interview ?
Seems like he never addressed scalability and availability in the design.
Also, didn't talk about sharding
Enjoyed the session,
also timestamp helps
What app is the interviewer using?
Hey Lee! The whiteboard app being used here is called Whimsical!
Should have gone deeper into Kafka and how orders are managed. Also, one of the biggest thing with hotels is location so he should have gone into that as well.
I won't go for BFF, To solve under fetching and over fetching issue, graphql is much better option instead of building out BFF for each UI. Too much overhead cost and even complicates the system.
🎉🎉🎉🎉🎉🎉