System requirements

Functional:

• Users can specify a starting point and a destination by typing addresses and ask for the shortest route and estimated time of arrival.
• The system provides both a textual and graphical representation of the shortest route in terms of time.
• The system provides the estimated amount of time required to take that path.

Non-Functional:

• Low latency.
• Scalability.
• Availability.

Capacity estimation

Estimate the scale of the system you are going to design...

API design

GET /route {

start_point

end_point

} - returns list os roads and estimates time to arrival.

Database design

We can represent map as graph , where nodes - road intersections and edges - roads with metrics (distance, speed limits, traffic data). Lets split graph on grid with layers, where layers represent : 1) local, small roads, 2 larger streets typically within a city, and 3 highways.

nodes_table (

node_id,

lon,

lat

);

edges_table {

edge_id,

source_node_id,

target_node_id,

length_m,

speed_limit_kph,

road_class,

is_one_way,

traffic_factor,

last_updated_at

);

High-level 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...

Request flows

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...

Detailed component design

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...

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.

Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?