Requirements

Functional Requirements:

• Log workouts
• View history & basic stats.
• Sync across devices.

Non-Functional Requirements:

• Availability: The System should be highly available.
• Consistency: System should be highly consistent where each activity reading should be capture and reflect on the user screen.
• Reliability
  1. The System should behave correctly and deliver the functional requirement even in case of failure, request spikes and other outage.

API Design

• Log a workout
  1. System should capture the user workout details.
  2. HTTP POST: /api/v1/workout
  3. Request Body: {

"workouttype":"".

"workoutmetadata":{}

}

d. Response: {status:"", message:""}

• Get the workout history
  • User can get the workout details by workout type, for a date and time
  • HTTP GET: /api/v1/workout/{workout-type}/{startdatetime}/{enddatetime}
  • Response: {workouttype:"", metadata:{}}
• Workout stats
  • User can get the statistics of the specific workout
  • HTTP GET: /api/v1/workout/{workout-type}
  • Response: {workouttype:"", metadata:{}}
• Synch the workout details with backend
  • The workout data will be store at the local storage for a specific interval or when the user is offline. once user is online of after a specific interval user data will be synch to the backend system
  • HTTP POST: /api/v1/workout/synch
  • Request Body: {

"workouttype":"".

"workoutmetadata":{}

}

• • d. Response: {status:"", message:""}

High-Level Design

1. Workout details of the user will be store locally and gets recorder every 2 seconds.
2. The workout details which is persisted locally will have a retention of 7-10 days depending on the local storage capacity.
3. By Maintaining the workout details locally user will get the latest data reflected without any lag.
4. The locally store data will be synch to the backend server once user is online or after a specific interval such as every 1 hours.
5. While synching the data the data will be sent as a batch and process in batch to achieve the low latency.
6. There will be a batches execute for each activities for a specific interval which aggregate the data and persist the summary of each user, so that user will get the workout summary report/statistic from the pre calculated data.

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.