BOOKMYSHOW System Design, FANDANGO System Design | Software architecture for online ticket booking
Vložit
- čas přidán 3. 08. 2018
- Learn how to system design BOOKMYSHOW or FANDANGO or Online ticket booking system.
One of the famous interview question in companies like Linkedin, facebook and many startups.
Here is the system design diagram : imgur.com/Ij2FqKs
#bookmyshow #systemdesign #architecture #interviewpreperations #amazoninterviews
#interviews #learnsoftwaredesign
Donate/Patreon: / techdummies
you are my new favourite on youtube. Keep up the good work. Thanks for such informative videos.
Great video, wanted to correct a wide-spread incorrect assumption about Relations in context of RDBMS. A "Relation" in RDBMS do not represent the relationship between 2 tables. Many believes thats the case. But Relation in RDBMS means a "Table". So all rows belonging to a Table is "related" set. In other words Table=Relation and it stems from the Set Theory.
Isn't it related to entity relation ship model? Which is relation ship between entities and entities represented by individual table?
@@aneeinaec relationship*** != relation
Real good video i saw every video of yours and it really helped me cracking interview of one of the big 4.. i used concepts of this video in my design n architecture, and it really helped me.. keep doing good stuff man..
This is one of the high quality system design content. Very useful. Thanks a lot.
As others mentioned, I'm also expecting LLD from you. As these days a lot class designs are expected during interviews, like designing a HTML parser, parking lot, ORM framework, DI container, unit testing framework.
Hi Narendra , you have explained the session very well. I am your consistent viewer/user and follow your all system design related series and concept.
This is a good example of how an SDE i/ii would design the BMS in an interview, as interviews would like the candidate to talk more about how the 15 mins locking period (book to pay) is implemented and how the tickets are not oversold when the QPS is super high. Narendra I'm wondering how would you do if you are asked to record this video again after 5 years, thanks!
Great video , best explaination i have ever seen for BMS on youtube. Thanks a lot
I can see you worked hard for this video
Very clear and easy to understand
Thanks for sharing
Absolutely Superb explaination in just 27 mins...i cleared most of doubts and gave knowledge on the latest techologies like NoSQL. Thank you, Narendra. Great job. May God bless u
Awesome!! Explained really well....Looking forward for many such videos
Nice video. Initially I thought he can't do it but I was wrong. It went very well. Nice. Looking forward for more such videos
Dharmendra Bhojwani Thanks a lot, am pretty new to explaining stuff and I am always open for suggestions. Please do suggest me some improvements.
You are really good in teaching.Please keep up the good work.It is helping millions of people like us to learn.
nice video, understood the basics of system design. Planning to read about each individual unit you briefed in the video.
Thanks for the detail explanation,it is very useful.
Great explanation of each comments, usage and use cases etc... Keep it excellence work...
Love the dog barking on the background. These are great series. Thank you so much for simplifying the interview process.
Short and simple - Thank You Narendra :)
awesome detailed explanation cleared lot of technology doubts as well.
Like your indepth knowledge and explanaitions!
Doing great job !! Thank you :)
This was really helpful.
awesome ..covered almost all design aspects..
In the architecture, the ELK stack is generally to be used for server log aggregation and searching. For Searching, You might just need any indexing database like Lucene based Solr, Elastic. The data can be indexed to the search databases from the transactional systems using a pipeline.
Does ELK forms Elastic search,Logstash and Kibana? Why again separate specification of Lucene or its derivatives? Pls clarify
@@vishnuv4813 Yes both of them can be Elastic search. But it is better to maintain separate instances of Elastic search for logging and Application search for the sake of separation of concerns. Logging might be huge data, application search might have relatively less data. If you have the same search database for both, you might face noisy neighbor problem i.e log data causing slowness in the response of the application. Micro services architecture prefer separate databases for separate services.
Thanks for nicely explaining each and every details.
Great video. lots of information very well explained. Good work. Thanks. You could add a little bit more details on SQL and NoSQL data modelling along with entities you covered it would be great.
Great content ... very well explained in simple terms and at perfect pace.....
Impressed, It has huge information bro
great job in detailed explanation
Great video.
I want to understand more about scaling a SQL and No SQL database and how to overcome problems like Replication delay, Consistency, Transactions and Different locking strategies on a highly available distributed database. Please can you make a video explaining this only.
Thanks
Your system design videos are very good. Please do more.
Thanks a lot, and sure I am working on it.
Thank you so much. This helped me !
Compared to other videos this lacks technical depth. How exactly locking happens , how theater API's works , why do we need logstash etc are required in my opinion
Locking probably at database isolation level via read committed technique
locking is database concept with verious lavel ex. write lok,read lock,both ....
Thanks for such valuable information and time brother. :)
Excellent explanation as usual! Subscribed to channel.
Thanks alot
Very well articulated. Thanks
Superb Video and Explanation, thanks for continued help.
I have been lately following your system design videos which have good meat in it.
Specifically for this video, I feel it could have been made better focusing on the crucial information
- Strong Consistency handling with Optimistic Concurrency Locks, how it fits into this use-case
- Good reasoning around the choice of DBs for Search and Booking and how does the data synchronization happen between the two
- Pub-Sub model when we publish single booking event and how it will be interpreted by its subscribers for its own use-case such as notification, analytics etc..
- Reasoning covering the choice of the DBs such as CAP theorem fitment, scale, schema flexibility, data distribution
- Clear separation of Functional and Non Functional requirements
Yes specially booking the same seat by users, suppose your system is getting 100k request per day How you're going solve this problem ???
Great question. @TechDummiesNarendraL Would like to hear your solution to this problem
Very well explained :)
Thank you so much for your work 😌 Very educative
Thanks for the video. I was looking for system design for 1. Google Maps 2. E-commerce website like flipkart. It will be great if you please make videos for those. Keep up the good work. Thanks.
Love your efforts
Superb ! Great video.
Very useful video tqsm bro
Great videos. Your videos helped me crack interviews at Amazon and Goldman Sachs. Thank you❤️
Great stuff. Thanks
Nice informative video from beginner perspective.
very informative, thanks a lot :)
I watched your other system design videos which are great. But I feel this one could be better if you would have focused more on the microservices which we will have in this use case and how they are interacting to fulfill our requirements. And less focus on specific technologies. The system design diagram looked more generic which should highlight more on solving the business problem.
i agree with Vivek here. This is a very generic design. you should put in the service names naming which one handles what responsibility . You also have mentioned nosql and cache. would have been better if you started simple and then address how adding these 2 will address the problems related to speed and concurrency.Try #CodeKarle channel's system design for air bnb its quite similar question about tkt booking and he has explained it much more better.
Very detailed. Thanks
Great explaination ....hats of🤓🤓🤓🤓
awesome video thank you so much
Great video, great explanation
One of the best!
You are doing a good job explaining high level overviews of architectures. This can be improved by reducing each video to byte-sized videos based on a concept or by provding duration markers.
Yeh, you are right. Time consuming but possible. Considered :)
Excellent explanation - thanks a ton for this! :)
I had a quick question - can we place Varnish in front of the Load Balancer?
Thank you for this video.
Really Nice video and explanation
You rock man.
Very clear system design
Superb explanation
great work keep it up
great job! sir
@Narendra L : Awesom set of videos. Please make a video on designing train reservation system (irctc) , Asked in Amazon multiple times.
Hey, very helpful video thankyou for this one. Though, it would be great if you can make system design video of make my trip.
Good informative video
Excellent
How to handle when other platforms books ticket. How to update the seat chart please explain that. This is very simple what you explained
Big thumbs up!!
Hey Naren .. 1) in the beginning of the video you mentioned theatre DB. Does that mean the db owned by theatre (and not BMS) ? So any db that needs to on-board to bms should expose lock api right ?
2) there is a db schema that you mentioned at the end. So these tables owned by bms will be maintaining a replica of some details like available seats etc which already is stored in theatre db is it ?
Can you please help in differentiating between theatre db and db owned by bms ?
correct .. i too have the same doubt ...
Thank you for such a detailed explanation
I have two queries
1. As you said there is relationship between entity like movie,Cinema etc that is why we should choose RDBMS,But if read to too heavy should not we choose denormalized database design? As Music player has been designed in Cassandra's official blog. Where as per query table has been designed, of course for booking we can go with RDMS because it will need transaction.
2. I have seen different blogs where they have explained to first calculate TPS and DB sized required,It is really required in interview to calculate tps and db size
1. Yes you are right RDBMS is must when you need transactions.
In case of MOVIE->ACTOR relationships you can use De-normalized database tooo(depends of size and QPS) or you can use RDBMS and a caching layer if reads are more.
It is absolutely possible to build relationships using Cassandra with proper data-modeling.
2. It depends, please clarify it with interviewer before you answer(its always good to have DB size calculation as it gives you an idea of what kind of DB you should go for). I also including DB size and TPS/QPS information in recent videos too.
Great video ..this was very helpful. Can you do a system design video explaining docker and kubernetes in detail? Thx
Very Good Information. Thank you so much for the nice content. One question from my side. U have mentioned that we can user elastic search for searching of movies, theaters, etc. So from where the elastic search will consume the data..? I mean what will be the input data source?
Hi Narendra,
Thank you for the insightful video on system design. However, I wanted to point out that BookMyShow primarily functions as an aggregator. Therefore, the actual seat availability and booking processes are likely managed by third parties or partners, such as Inox, who handle the ticket reservations. Could you consider creating a video explaining how such aggregators communicate with multiplexes or chains of multiplexes, how they display showtimes and seat availability in real-time, and how they facilitate real-time ticket bookings?
Please include class diagram, database design and also some basic coding for all the system design . That will help much to visualize all the things behind the scene.
Nice video, Can you please add video for retail website like amazon, When they will have sales how they will manage lots of request and availability of item for particular pin-code and how they will decide one day delivery of item. It will be very helpful if you will add this. Thanks
This is a sure fire way to flunk a system design interview. System design interviewers generally look for the application specific design details rather than bunch of product/technology propositions. Buzzwords without substantiation raise an immediate red flag.
What buzzwords did the presenter use exactly? Is it a database, cache, server, load-balancer or locking? The video covers a 10k feet view of a system. it doesn't need to be very specific. It's abstracted but solves the problem.
Completely Agree, This may be covered in the first 10 minutes as a High-level Application design.
But Any actual interview would involve Data model (Entities + Relationships), API, Concurrency and so much more.
This video taught me absolutely nothing I didn't know from working as an engineer in the first place
Thanks. This is really great. One question. When you walked through user flow towards the end, you didn’t tell how the backend RDBMS comes in play. Kindly elaborate
Excellent..
AWESOME
Good explanation but you have overwhelmed me with thought, I will recommend initially focusing on one problem design bookmyshow and then jumping into the concept of Market Place. even Amazo has the problem of inventory and sometimes you may get a theatre which doesn't have an online system but they are still selling their ticket on multiple site .
Nice Stuff
Awesome explanation..just one quick question which I have is..how to handle increased number of users logging in accessing the booking flow from concurrency perspective..thanks again mr. Naren
Thank you for the video - I love how you did the diagram of all system components. Can you do a follow-up material on how to support that ticket reservation (in more technical details)? I've done an interview with Google recently, one engineer asked this sys desing question, but drilled in depth on that ticket reservation. Details from my interview - user can book up to 10 tickets (sets) at the time, it's reserved for him fo 2 minutes, there must be no collistions (like user 1 sees seat A23 as available, then spend 1 minute to fill the info, but the same seat booked by other user 2 and user 1 got error response)
I guess following will happen:
1. Call theater's API to get available and booked seats for a movie+show-date-time combination for a theater in a city.
2. User chooses and selects the seats. clicks next.
3. Call Hold API for the selected seats (Hold for 5mins), it'll appear as booked to any users who tries to see available seat. if unavailable return error to user and let them select other seat/
4. let the user fill all the details, login if was not loggedin, add payment details.
5. This is optional - verify credit card and place hold. if payment can't me held show error to user and let them enter a new credit card.
6. validate seat can be booked and still has hold, if unavailable return error to user.
7. collect payment, if payment can't me collected show error to user and let them enter a new credit card.
8. Mark seat as Booked in theater.
9. Return confirmation to user.
Do they use API's to access the theatre's inventory or DB Connectivity?
great !!!
Hey Narendra ... good learning for me by watching this video. You explained in a very good way. Could you please help me by letting me know from where should I check the further design details i.e. low level design
Hi Narendra, You explained very well. Well, the basis on the explanation, Would you please cover the scenario that If, the theaters would have their own booking system and they are taking bookings from various sources such as Book my show, Paytm and so on then how it would work ? Also, the counter question is.. how to handle the same request at the same time from two or more sources?
Hi Naren, Thanks for the detailed explanation. Can you please create a video for ticket booking system from Theatere side.
Thanks a lot for the information. This was very useful. I just have a quick question on the theater server side. Who maintains information on the theater server side? In case of BMS, do we have a generic API in the theater side? Or do we have to implement it in the theater side as well if we have to support a particular theater?
PVR/INOX like big theaters companies have their own ticket booking application, so as a theater aggregator service we need to work along with their system/APIS.
But some small scale theaters will not usually have ticketing systems. in that case we will have to provide some sort of service/server to let them know what tickets are occupied/free.
very useful.
Please add information about movie timings as well, rest all is helpful. Thanks a lot.
Thank you
Hi Narendra , I am big fan of your system design videos. I have question here. Since BMS follows micro service architecture, a comment or like by 2 users(geographically located at 2 different places) may be handled by two different servers. Then how does system ensure the consistency for number of comments/likes. Will system be eventual consistent ?
It was great thanks brother really appreciated
Can you please break the design into microservice? Thank you for all your efforts. It is really worth watching.
Great video!! I had been asked this question in Amazon's interview for SDE2 role. They expect a lot much from a low-level design perspective like class diagram. You mostly cover HLD please cover component level design as well. Thoughts??
Shashank Urade I think the fields/class diagram is very simple. He’s mostly teaching architecture design. If you understand all these, try to shoot for a SDE3 or Principal SDE in Amazon and they’ll ask you the same.
Can you please do a system design video on how a global distribution system (GDS) for travel works. It would be very helpful. Thanks
This is nice. I see app servers never talks to rdbms or nosql db directly. There could be lot of scenarios where I have to hit db directly instead of always the cache route.
Small correction, finally you said you are processing the log data using ELK. Initially you told you do user search for movie using elastic search. As per the design it should be queried and cached right. If we have that information in elastic search, it should be feeded in the form of some data which should not be from log
If we want to store movie information in elastic search for faster search,can we store directly or does it has to go through logstash?I mean log stash is meant for this or only for logs purpose?