Requirements

Functional Requirements:

• User should be able to start,pause and stop his rides/running basically log his workout
• User should be to view his activities and also activities of his friends
• User should be to get real time details like distance,route regarding his ride/run
• Sync need to sync across devices when users are offline

Non-Functional Requirements:

• Availability >> Consistency ( The workout logs should be highly available but eventual consistency of a few secs is acceptable.The avialbility uptime percentange needs to be atleast about 3 nines.
• There should be low latency for user to get his details like speed,distance covered,elevation gain etc during ride
• User should be to get details like distance,router etc even while its offline
• Uploads of data should be idempotent
• Scalable upto 10 million activities

Core Entities

• User
• Activity
• Route
• Friend

API Design

• User should be able to start,pause and stop his rides/running basically log his workout

POST api/v1/activities -> activity

{

type : "ride"|"run"

}

PUT api/v1/activities/:activity_id -> activity

{

state: "start|pause|stop|completed"

}

POST api/v1/activities/:activity_id/routes -> activity

{

location: GPSCordinates

}

• User should be to view his activities and also activities of his friends

GET /activities?mode={USER|FRIENDS}&page={page}&pageSize={pageSize} -> Partial[]

// To get details of a particular activity

GET /activities/:activity_id

• User should be to get real time details like distance,route regarding his ride/run

GET /activities/:activity_id

• User need to sync across devices when users are offline

POST api/v1/sync/apple_health

POST api/v1/sync/garmin

GET api/v1/activities/export -> API to download activity data

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.