System requirements

Functional:

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

1) track physical activities

2) set goal

3) monitor progress

4) user login and session management

Non-Functional:

List non-functional requirements for the system...

1) scalability

2) availability

3) low latency

Capacity estimation

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

API design

Define what APIs are expected from the system...

Database design

the database design i have used relation i have made three table

one for user that store user specific data like person details and

after that there is activities tables that store list of activities opted my user . there is activity record in this table i will store activity data point .

• Users Table: user_id (PK), name, phone_no, email, password_hash, created_at, updated_at
• Activities Table: activity_id (PK), user_id (FK), activity_type, start_time, duration, distance, calories, created_at, updated_at
• ActivityRecords Table: record_id (PK), activity_id (FK), timestamp, heart_rate, steps, created_at, updated_at

}NoSQL Database

• Utilize a NoSQL database like MongoDB for storing large volumes of unstructured or semi-structured data, such as detailed sensor data or logs from wearables. This ensures flexibility to handle sensor readings with varying attributes.

Caching Layer

• Implement a caching layer, likely with a tool like Redis, to quickly compute and store user statistics (e.g., weekly progress) every time a new record is created. This cached data can then be used to swiftly populate users' performance stats on the app.

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?