🏛️ System Architecture Overview

Migraine Tracker is built on a modern, decoupled architecture designed for speed, security, and scalability. Because we handle highly sensitive health data, our system is strictly segmented to ensure encryption boundaries and data isolation.

Here is a high-level look at how all the pieces of the Migraine Tracker ecosystem talk to each other.

🗺️ The Ecosystem Map

┌─────────────────┐       OAuth / JWT       ┌──────────────────┐
│                 │ ──────────────────────> │                  │
│  React UI App   │                         │  Supabase Auth   │
│  (Vite + TS)    │ <────────────────────── │  (Identity)      │
│                 │          Token          └──────────────────┘
└───────┬─────────┘
        │
        │ Bearer Token (HTTPS)
        ▼
┌──────────────────────────────────────────────────────────────┐
│                       NESTJS MONOLITH                        │
│                                                              │
│  ┌──────────────┐   ┌───────────────┐   ┌─────────────────┐  │
│  │ User / Auth  │   │ Incident API  │   │ Health Logs API │  │
│  └──────────────┘   └───────┬───────┘   └─────────────────┘  │
│                             │                                │
│                     ┌───────▼───────┐                        │
│                     │ Pattern Guard │ (Predictive Engine)    │
│                     └───────┬───────┘                        │
└───────┬─────────────────────┼────────────────────────┬───────┘
        │                     │                        │
        │ AES-256             │ HTTPS                  │ Mongoose
        ▼                     ▼                        ▼
┌─────────────────┐  ┌──────────────────┐  ┌───────────────────┐
│                 │  │                  │  │                   │
│ Cloudflare Edge │  │  External APIs   │  │   MongoDB Vault   │
│ (Key Rotation)  │  │ (NOAA, Meteo...) │  │  (Data Storage)   │
│                 │  │                  │  │                   │
└─────────────────┘  └──────────────────┘  └───────────────────┘

🧩 The Core Components

1. The Frontend (React + Vite)

The user-facing dashboard where tracking happens. It is built as a Single Page Application (SPA) using React 18, Vite, and Tailwind CSS. It communicates directly with Supabase for authentication, and passes the resulting JWT to our NestJS backend for authorized data fetching.

1. Identity Provider (Supabase)

We offload password management and OAuth (Google/GitHub) completely to Supabase. This means our core database never stores user passwords.

1. The Backend Monolith (NestJS)

The brain of the operation. This Node.js/TypeScript server handles all business logic, data validation, and houses the Pattern Guardian—our proprietary engine that cross-references user health logs with environmental data to predict pain triggers.

1. External Environmental APIs

To feed the Pattern Guardian, the NestJS backend asynchronously pulls localized weather and solar data from APIs like Open-Meteo, NOAA, GFZ, and TEMIS.

1. Encryption Edge Worker (Cloudflare)

To keep health data ultra-secure, specific payloads are encrypted at the application layer before saving to the database. The symmetric keys required for this encryption are generated and rotated daily by an isolated Cloudflare Worker running at the edge.

1. The Database (MongoDB)

A NoSQL document store that holds the encrypted health logs, incident histories, user configurations, and the predictive rules generated by the Pattern Guardian.