Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
- Customer opens up mobile app to look at restaurants in their area
at a particular time
- Search for keywords
- Customer adds an item to their order, initiates order from that Restaurant
- Customer can finalize order, lock in delivery instructions, pay for food
- Restaurant makes food, gives it to Dasher, Dasher delivers the food to Customer
- Restaurants might have multiple orders - prioritization (order placed, flexibility... depends)
- Dashers might have multiple orders at the same time - prioritization necessary, geolocation part
- immediate delivery, not pickup
extended:
-Payment black box
Customer confirms food was delivered, leave a Review
-Signup taken care of
List non-functional requirements for the system...
- Availability: highly available -- most necessary half end of the event (there are phases of delivery), dasher location
- Consistency - read after write consistency, after delivery can write more details
- Persistence - some permanent records, though we potentially get rid of records after some time.
- higher statistical proability of reads within first 48 hours
- Scalability - prioritization
Estimate the scale of the system you are going to design...
Define what APIs are expected from the system...
Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...
You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...
Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...
Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?