How cssfr/fastapi-poc-backend works
Main components
a. API Layer
• FastAPI app (“app/main.py”)
• Middleware, authentication (app/auth.py, app/middleware.py)
• Routers:
– OHLCV router (app/routers/ohlcv.py)
– Storage router (app/routers/storage.py)
• Health check endpoint (app/health.py)
b. Service Layer
• Business logic (app/services.py)
• DuckDB analytics service (app/duckdb_service.py)
• Supabase Storage client (app/minio_client.py)
c. Data Persistence
• PostgreSQL (Supabase) via SQLAlchemy (app/database.py, app/models.py, app/models_ohlcv.py)
• Migrations (alembic/ + alembic.ini)
d. External Services
• Supabase Postgres (env var DATABASE_URL)
• Supabase Storage (S3-compatible; auth via SUPABASE_URL + JWT_SECRET)
e. Dev/Deployment
• Dockerfile & start.sh
• .devcontainer for VS Code
• Requirements.txt, uvicorn run command
Relationships and data flows
• Client → FastAPI (uvicorn) → Routes → Services →
– ↳ PostgreSQL (read/write via SQLAlchemy)
– ↳ DuckDB (for analytics queries)
– ↳ Supabase Storage (via MinIO client for object upload/download)
• Alembic migrations run against PostgreSQL at build/deploy time
• Health check and logging are cross-cutting concerns
Architectural patterns
• Layered architecture:
– Presentation/API layer (FastAPI + routers + middleware)
– Service/Domain layer (business logic, data-access services)
– Data layer (ORM models, migrations, external DB/storage)
• Dependency injection/configuration via environment variables
• Separation of concerns:
– Auth, Logging, Health, Business, Data