System Design of a Delivery System like Zomato with

No video

System Design of a Delivery System like Zomato with

Рет қаралды 19,553

Күн бұрын

In this video, we look at what powers the delivery and tracking systems of e-commerce apps like Zomato, Swiggy, and Amazon.
Along the way, we go through relevant spatial algorithms, network protocols, and design components used in location-based systems.
Cheers!
00:00 Problem Statement
00:45 Requirements
02:00 High-Level Design
04:01 Capacity Estimation
05:36 Location-Based Queries
13:30 Tracking riders
20:00 APIs
24:05 Conclusion, thank you!
Quad Trees: • Designing a location d...
System Design Course at InterviewReady: get.interviewready.io/
Designing Data Intensive Applications Book: amzn.to/3SyNAOy
You can follow me on:
Github: github.com/InterviewReady/sys...
LinkedIn: / interview-ready
Twitter: / gkcs_
#SystemDesign #InterviewReady #Coding

Пікірлер: 18

@KeertiPurswani 4 ай бұрын

Absolutely love recording this series! The discussions are so raw and real, hope you all are also liking it!

@rishiraj2548 4 ай бұрын

Yes... Great thanks

@rishabhbafna36 4 ай бұрын

12:55 Here in the cache you can store the data in a priority queue like data structure in low level, where the nearest, best rated and fairest top riders let say 10 will get the notification of the order. And If non of them accepts for say 1 minute, than next 10 will be shown. This way we can limit the size of the cache and fetch the top required data from the central db in the memory.

@arunavasaha7051 Ай бұрын

Yes, thats great idea

@andw2001 4 ай бұрын

Congrats Guys, could get a lot of insight from this talk! Rock on! 😁

@RAZREXE 4 ай бұрын

Amazing video as always, thanks Keerti and Gaurav

@user-zk1zm6sm2u 28 күн бұрын

Interesting design and discussion.

@bagirathan8350 2 ай бұрын

don't you think for updating the location its better to have a seperate service where delivery partner sends location updates to which updates the cache instead of delivery matching service since it could have a lot of persistent connections and can be scaled independently, because there may be few orders in a day and some days can have large orders which would make the load on delivery matching service quite high, because anyway we have to update the location of drivers, or am i missing something?