Requirements

Functional Requirements:

List the key functional requirements for the system (Ask the AI for hints if stuck)...

1. The user can see the weather by city or latitude and longitude
2. The user can also see the weather for past and future dates, with predefined options.
   1. Past predefined options - yesterday, last week, last month, last quarter, last year.
   2. Future predefined options - today, tomorrow, current week, next week, current month, next month, Next quarter, next year.
   3. custom dates with defined past and future dates. till when we have data. This also includes timezone info.
3. Users should be able to see weather information in their preferred language.
4. Users can see the weather for hours as well
5. Users can see the weather forecast for humidity, wind, air quality, and precipitation.
6. There is no need to log in to see weather information, but when the user wants notifications for future dates, then they can create their profile over our platform and subscribe to get notify their preferred city weather for future dates. These preferences can be saved into our database.
7. The notifications system can send push notifications such as email, social media, and text message.
8. Data security
9. Users can share or download weather reports in csv or html format.
10. Users can log in with google identity service for easy sign-in/sign-up.
11. Sign up with email/mobile number
12. Records can be stored in the Redis cache for increased system latency.

Non-Functional Requirements:

List the key non-functional requirements (performance, scalability, reliability, etc.)...

1. The system should respond within a 1-second latency

2. The system can be scaled up/down as per traffic

3. Fault tolerance

4. System uptime

API Design

Define the APIs expected from the system. This is your chance to analyse and define the read and write paths so that you can come up with the high-level design...

Controllers

1. Weather controller

1. GET - Api/v1.0/weather/cityname
2. GET - Api/v1.0/weather/predefineddates
3. GET - Api/v1.0/weather/customdates

2. Account controller

1. User login
2. User sign up

3. Notifications controller

1. 1. Send notifications

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

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.