
🏅 Sports & Fitness · Deployment · Pro
Where each part of a fitness tracking product runs: the wearable, the phone app that syncs it, and the cloud services for workouts, goals and coaching.
Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.
Drawing diagram…
Deployment for a fitness app with wearables: a smartwatch/band records heart rate, steps and sleep and syncs over Bluetooth LE to the phone app, which stores data offline and uploads batches to the cloud API. In the cloud (Kubernetes): API gateway, activity service, goals and challenges service, coaching service with ML recommendations, a sync service for Apple Health / Google Fit, a time-series store for sensor data and PostgreSQL for user profiles.
flowchart TB
subgraph Wrist[On the user]
W[Smartwatch / Band]
end
subgraph Phone[User's phone]
APP[Fitness App - offline store]
HK[Apple Health / Google Fit]
end
subgraph Cloud[Cloud - Kubernetes]
GW[API Gateway]
ACT[Activity Service]
GOAL[Goals and Challenges]
COACH[Coaching Service - ML]
SYNC[Health Platform Sync]
TS[(Time-series Store)]
PG[(PostgreSQL - profiles)]
end
W -.Bluetooth LE.-> APP
APP --> HK
APP -->|HTTPS batch upload| GW
GW --> ACT
GW --> GOAL
ACT --> TS
GOAL --> PG
TS --> COACH
COACH --> GW
HK --> SYNC
SYNC --> ACTHow live scores reach millions of fans within a second: official scorers, the data feed, stream processing, caching and push notifications.
A platform to run an amateur or professional league: team registration, fixtures, match scoring, standings and fan apps.
How a fan books tickets for a big match: queue, seat selection with a temporary hold, payment and a mobile ticket with QR code.
A timeline for organising a multi-team tournament: registrations, league stage, knockouts, final and the work around it.
A schema for a sports league: teams, players, squads per season, matches, match events and player statistics.
The states of a gym membership: trial, active, frozen, expiring, renewed, lapsed and cancelled.