Requirements

Functional Requirements:

• Log workouts
• View history & basic stats.
• Sync across devices.
• Integration with smartwatch
• data display
• User experience
• Device Integration:
• Real-Time Data Syncing

Non-Functional Requirements:

• reliable: it must give the user the correct information about the health services.
• latency: it must be low-since it must have the insights of the device (heartbeat, stress, etc)
• fault tolerance: sometimes the user doesn't have the internet, so it must save the analysis in the watch.
• performance: it must have a performance of 99% so it can return the hearbeats, burned calories, etc etc.
• Scalable: the system must behave correctly when millions of users are using it.
• High Availability: This ensures that the system is operational and accessible when needed.

API Design

For creating a user

post/v1/createProfile

put/v1/users/{id}

created endpoints for creating a profile

For the IoT device to the app it would be

get/v1/analytics

post/v1/analytics

For example, a watch would send that information to the app, since the user wants to see the distance, how many calories burned in the workout, the analytics.

from the app to the microservice to save it to the bd

get/v1/distance

get/v1/caloriesBurn

get/v1/time

get/v1/analytics

it would be kinda the same

High-Level Design

Users authenticate securely through an Identity Provider before accessing the application.

IoT devices continuously collect fitness data such as heart rate, steps, and GPS location.

The Mobile App displays workout information and receives live updates from the backend.

A WebSocket Gateway enables real-time communication between IoT devices, the mobile app, and backend services.

The Microservice processes business logic, including workout tracking and activity calculations.

An API Gateway serves as the centralized entry point for client API requests and routes them to backend services.

Redis is used as a cache to improve performance by storing frequently accessed and temporary data.

A NoSQL database persists application data, including user profiles, workout history, and activity records.

A Notification Service sends push notifications for workout milestones, reminders, and achievements.

The architecture is modular and scalable, allowing each component to be independently maintained and scaled based on demand.

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.