Requirements

Functional Requirements:

• Allow users to query current weather conditions (temperature, humidity, wind, etc.) for a specific city, coordinates, or region.
• Provide weather forecasts for upcoming days (e.g., 7-day or hourly forecast) so users can plan ahead.
• Enable users to look up weather by city name, zip code, or latitude/longitude coordinates.
• Push notifications, alerts, or live data updates to users when weather changes or severe events occur.

Non-Functional Requirements:

• Availability: The system should be highly available.
• Reliability
  1. The System should behave correctly and deliver the functional requirement even in case of failure, request spikes and other outage.
• Scalable: System should be highly Scalable for 100M users and be able to tolerate request spikes.
• Latency: The Read and write request should have very low latency.

API Design

• Weather Lookup

HTTP POST: /api/v1/current/weather

Request Body: {

"city":"",

"zipCode":"",

"latitude":"",

"longitude:"",

"region":""

}

Response: {

"temperature":"",

"humidity":"",

"wind":"",

"precipitation":"",

"city":"",

"description":"",

"weather_type":"SUNNEY/COLUDY/RANING/COLD"

"icon":""

}

• Weather upcoming Lookup

HTTP POST: /api/v1/weather/

Request Body: {

"city":"",

"zipCode":"",

"latitude":"",

"longitude:"",

"region":"",

"start_date_time":"",

"end_date_time":""

}

Response: {

"start_date_time":"",

"end_date_time":"",

"weather":[{

"temperature":"",

"humidity":"",

"wind":"",

"precipitation":"",

"city":"",

"description":"",

"weather_type":"SUNNEY/COLUDY/RANING/COLD"

"icon":"",

"hour":"",

"day_time":"AM/PM"

}]}

• Subscribe/unsubscribe for notification/notification

HTTP PATCH: /api/v1/weather/subscribe/{email}/{flag}

Path Parameter:

email: User Email

flag: SUBSCRIBE/UNSUBSCRIBE

High-Level Design

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.