How dxzielinski/ai-driven-financial-analysis works
This repo is a GCP-based, full-stack cloud application that provides AI-driven financial tips and saving plans from user transactions. The file tree strongly suggests three major concerns:
• aidfa-frontend/: user-facing web UI (likely SPA)
• aidfa-backend/: API + business logic (transaction processing + AI prompt/orchestration)
• aidfa-terraform/: infrastructure-as-code provisioning on Google Cloud Platform
How to mine the repo for the *actual* architecture (avoid guessing)
Because the top-level tree doesn’t expose frameworks/services directly, use the repo itself to drive accuracy:
Use Terraform as the source of truth for cloud components
In aidfa-terraform/, enumerate:
• Compute: Cloud Run / GKE / App Engine / Cloud Functions
• Data: Firestore / Cloud SQL / BigQuery / Cloud Storage
• AI: Vertex AI (Gemini) / custom model endpoints
• Messaging/Batch: Pub/Sub / Cloud Tasks / Cloud Scheduler
• Security: IAM service accounts, Secret Manager, VPC, Cloud Armor
• Edge: Load Balancer, API Gateway, Cloud CDN
• Observability: Cloud Logging/Monitoring, Error Reporting, Trace
Inspect backend for runtime and boundaries
In aidfa-backend/, identify:
• Entry points (e.g., main, server, app, index)
• API style: REST/GraphQL
• Auth middleware (JWT/Firebase/OAuth)
• Modules for:
• transaction ingestion/normalization
• categorization/analytics
• AI prompt building + response parsing
• persistence layer (repositories/DAOs)
• Outbound integrations (bank APIs, LLM APIs, email, etc.)
Inspect frontend for hosting and API usage
In aidfa-frontend/, identify:
• SPA framework (React/Vue/Angular/Next.js)
• Where it’s hosted (Cloud Storage+CDN vs Cloud Run SSR, etc.)
• How it calls backend (direct HTTPS, via API Gateway)
• Auth flow (Firebase Auth, Google Identity, custom)
These become UI + edge flow elements.
What I would expect the final “ma
A single page with:
• Left: User browser
• Middle: Frontend hosting + edge
• Right: Backend API + worker(s)
• Bottom: DB/storage + Vertex AI + async services
• Side: Secrets/IAM/Monitoring attached to backend