System requirements

Functional:

List functional requirements for the system (Ask the chat bot for hints if stuck.)...

Current weather information

2 Weather Forecast

3ocation Search

4 Personalization

5 API Integration

Non-Functional:

List non-functional requirements for the system...

1 System should be highly scalable

2 System should be fault tolorrent

3 system hound have low latency

Capacity estimation

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

Let’s assume there are 10^8 DAU the qps 10^8 /10^5 =10^3

API design

Define what APIs are expected from the system...

1. /v1/current-weather-info returns the current weather info for a particular city returns status code 200 if entered city is correct else will return 404
2. /v1/add-favorite adds a city as favorite returns 201 if adding favorite was successful else will return 503

Database design

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

As the system is write heavy as every second the weather can change so we will use nosql daytabase like mongodb which will have the following structure

{

“_id”:,

”temprature”:

”wind”,

”humidity”,

”precipitation “

}

this will be sample structure of the document

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?