Uber System Design | Ola System Design | System Design Interview Question - Grab, Lyft

preview_player
Показать описание
This is a solution for System Design Interview Question where you need to design a Cab booking System like Uber/ Ola/ Grab/ Lyft, etc.

Recommended Videos to watch before this:

If you like this video, please help us grow by sharing this video with your friends on Facebook, connections on LinkedIn and anyone who can benefit from this.

PS: This is not the real architecture of any such platform. This is my take on how I would answer that problem.

#codekarle #systemdesign #ubersystemdesign #system #design #interview #amazon #faang #Uber #Ola
Рекомендации по теме
Комментарии
Автор

Bro you are fantastic. So today I had an interview with MSCI (Morgan Stanley) and they asked me about designing around Ola, where they wanted me to show the cabs around a user as soon as he logins to the app. I remembered this video of yours and explained how things work and how the mapping service would divide the city into grids and fetch the information. The interviewer was satisfied and I feel I have cracked the round. All thanks to you \m/

puneetapiit
Автор

What an amazing explanation to the most complex of things. Teaching is an art, and it does get exemplified by your teaching style.
Kudos to you man

abhinav
Автор

Great video on two main dimensions that makes it easy to follow and appreciate:
1. Scope of the product is clearly defined
2. Delivery of content is very crisp and to the point

Cant stress how many other videos out there have a catchy title like "Design Uber service" that goes all over the place in terms of what it wants to cover and how to delivery the content. This is the best video on Uber System design available on YouTube.

sanmeet
Автор

It would have been great if you had covered how the request for cab is fanned out to multiple drivers and once any one driver accepts the trip, how the request is dropped from all the other drivers. overall content is very good and helpful. Very good effort.

keerthikanthchowdary
Автор

All your videos are very good. They are good to think about various requirements, splitting a given problem into multiple services and so on. But I think you haven't been talking about the data model, how it can be represented in a NoSql vs RDBMS vs graph database, and so on. Many interviewers expect that discussions, if not all. Hope you can do that in your future videos. Thanks!

rptok
Автор

You are an amazing teacher. Why have you stopped making such an amazing videos . Kindly create contents of top quality. You rock

prashub
Автор

This is the best video for uber system design out there!

mohitkalra
Автор

man, you are real good. seems you have worked at Uber or 1 of these cab apps, and have great understanding of when/where to use different tools/databases. thx much! But 1 point these are so detailed (including the time that would take to draw each of those layouts and bullet points), and some of these sys design interviews are only for 45 minutes (which actually may be only 35 minutes leaving the 5 minutes each for intro/outro), can't cover everything, but we can at-least layout the buffet of knowledge we have and let them pick what they would want us to go over.

ravig
Автор

I watched a couple of videos on Uber system design and wasn't satisfied and luckily ended up here. Very good explanation focusing on key components. Thanks bro !

evkumar
Автор

This video is very good. The best thing is that you have provided summary also with clear diagram.

Thank You very much.

mayanklalaiya
Автор

I think the complexity of maintaining redis to map driver id - handler and the reverse mapping also can be avoided.
If we load balance the request from driver based on driver id hash, the request will go to the corresponding socket handler, and when the response comes back say driver gets a ride booked, the driver object will have the id from which corresponding handler can be found. Thereby eliminating the need to store mapping.

AlbertoRodriguez-oejo
Автор

In many interview people ask algorithms in system design round. but I see your most of the design is like use kafka for self pace or decoupling, scaling. Redis for cache over mysql. It would be great if you can add algo in each explanation.

rabindrapatra
Автор

Fantastic bro. Your teaching style and kind of substance you produce is awesome!

KrithiHayagriva
Автор

Thanks Sandeep ... Such a great video. just one thing so customer also connects with Map service to find out its location + the A(pickup) and B(drop point) point

sonufarkya
Автор

Hi, thanks for the content on this channel! Had one question though.. in the customer flow, we will need a load balancer that makes a web socket connection to the cab request service right? Since there can be multiple customer requests at the same time?

thinktough
Автор

Very good explanation...all scenarios covered.

TheVergilfrans
Автор

Our college project is not real project but it gives some insight. Similarly this video is just an insight. I think uber is more complex designed.

RabindraPatra-ez
Автор

Why did you choose request response model for location update from driver? I think event driven model is more suitable for this. Please let me know your comments

manigandanganesan
Автор

when a new driver comes online and gets connected to a websocket, how the websocket manager gets to know the fact and how does it update mapping? Is it using internally a HashMap?

goutamkundu
Автор

Great video! Watched 3 other videos and this one is the best by far. One thing though is you never mentioned what Location Service will write to Kafka. Can you please clarify this?

ashleydorris