How hoangm416/lung-cancer-management works
Project Type and Purpose
• Full-stack web application for clinical/omics data analysis and visualization.
• Frontend (React + Vite + TypeScript + Tailwind) presents charts and tables.
• Backend (Node.js + Express + TypeScript) exposes RESTful APIs for user, record, research, analytics.
• Uses Supabase for authentication and a relational database (Postgres or similar) for persistence.
Main Components
A. Client / Browser
• Loads the React single-page app (index.html + static assets).
• Interacts via HTTP(S) with backend APIs and Supabase.
B. Frontend Application
• Vite dev/build server or static container.
• React components, routes (AppRoutes.tsx), UI (charts, tables, forms).
• Supabase client for sign-in, auth callbacks, ProtectedRoute wrapper.
• Static data files under public/data consumed for Kaplan–Meier plots.
C. Backend Application
• Express server (index.ts) in a Docker container.
• Controllers (AnalyticsController, RecordController, ResearchController, UserController).
• Models mapping to DB tables (user, record, research, gene, omics, etc.).
• Routes connecting endpoints to controllers.
• Auth middleware guarding protected endpoints.
• Utility scripts for data processing.
D. Database
• Relational DB (e.g. Postgres) storing users, records, research entries, omics results.
E. External Services
• Supabase Auth / DB if fully managed.
• Docker-Compose orchestrates frontend, backend, and database containers.
Relationships and Data Flows
1) User → Browser → React UI → Supabase Auth (login/register)
2) React UI → REST requests → Backend Routes → Controllers → Models → Database → Controllers → JSON responses → React UI
3) React UI loads static JSON/TSV files for exploratory charts directly from its public folder.
4) Docker-Compose manages network: frontend ↔ backend ↔ database.
Architectural Patterns & Design Principles
• MVC-style layering on the backend (Routes → Controllers → Models).
• Component-driven UI in the frontend (atomic UI, chart/table components).
• Separation of concerns: auth, API logic, data models, UI, static assets.
• Use of middleware for cross-cutting (authentication).
• Containerization (Docker) for consistent development/deployment.
Technologies & Frameworks
• Frontend: React, Vite, TypeScript, Tailwind CSS, Supabase JS SDK, Chart libraries (e.g., your custom BarChart, KaplanMeierChart).
• Backend: Node.js, Express, TypeScript, Docker, ts-node, dotenv.
• Database: PostgreSQL (or Supabase-managed DB).
• DevOps: Docker, Docker‐Compose.