Low Level Designing (LLD -4) - Food Ordering System | Low Level Design | LLD | Zomato | Swiggy #lld

#objectOrientedDesign #systemdesign #lowlevel

► ► Low Level System Design Playlist:

Low Level Designing is one of the most critical round for technical Interview, especially if you are appearing as an experienced candidate in any of the FAANG / product based organisation. And in this video tutorial serial we will see in detail, that how we should handle a designing question during our designing interviews. And how progressively ,we should gather our requirements and gather the information for the low level system designing.

In this video I have discussed about the Low level System design of the online food delivery app like Swiggy, zomato, uber eats, food panda etc.

*****************************
Difficulty: Medium
Topic: Low Level System Design
DS: Flight Booking System / MakeMyTrip
Company: FAANG
*****************************

#interviewWithBunny #techInterviewSystemDesign #crackingthetechnicalinterview

► ► Social Connect:

Additions Tags:
system design,low level design,system design interview,low level system design,low level design interview,low level system design udit agarwal,low level design interview questions,grokking the system design interview,system design tutorial,system design interview questions,low level design | the code mate,uber system design,low level design mock interview,low level design vs high level design,low level design soumyajit bhattacharyay, low level design,system design,system design interview,low level design interview questions,low level system design,low level design interview,low level design tutorial,system design interview questions,grokking the system design interview,system design tutorial,low level design | the code mate,amazon system design,low level design course,low level system design tutorial,low level system design udit agarwal,design,uber system design,zomato system design

[InterviewWithBunny]

► ► Low Level System Design Playlist:

[saranshagrawal]

Do orders really belong in the customer class? It violates Single responsibility principle I guess.
Imo, There should be a separate class called OrderHisoty which will have user_id & List<Orders>.

[Student__.]

I was so confused and never understood any of the system design concepts, but this video helped me understand everything so clearly. Thank you so much !

[vikramreddy]

This is the most underrated channel on LLD. Keep it up.

[rupeshjha]

Please keep on posting such awesome videos!
One correction would be in Map<Location, Restaurent> map ---> Map<Location, List<Restaurent>> map as one location can have multiple restaurents

[himanshusrihsk]

Explanation is really good. Thanks.
Please add more low level design problem

[saketvajpai]

Very simple and well explained. Thanks. Please keep posting such videos.

[LakshmikantDeshpandeu]

The videos are really awesome 🙌🏻
Keep up the good work mate…!!!
~Live To Code~

[AbhishekKumar-yvih]

Shouldn't Customer inherit from User?

[shankarbinnar]

I think missed the delivery partner aspect in the discussion

[rhimanshu]

Could you also add the design patterns which can be used . That will add more juice to the LLD

[malayrevanth]

Shouldn't menu be a seperate entity ? You are voilating the SRP principle by adding updateMenu() definition in Restaurant class.

[ishortharu]

Sir plz make video in netflix clone with using spring boot.