How jainsamyak15/chat-csv works
Project Type and Purpose
• This is a full-stack, local-only, chat-based data analytics web application.
• Built with Next.js (React + API routes), SQLite (via Prisma), Redis for caching, and a locally hosted LLM (Ollama).
• Users upload CSV files, interact via a chat interface, and view interactive visualizations.
File Structure Analysis
• Top-level config: Dockerfile, docker-compose.yml, next.config.mjs, Prisma files under /prisma, Tailwind and PostCSS config.
• Frontend & Backend combined under /src/app:
• React pages/layouts in app/layout.tsx, app/page.tsx, components under /src/components/ui, chat, upload, visualization.
• Next.js API routes in /src/app/api: chat, chat/messages, files, upload, visualization.
• Generated Prisma client under /src/generated/prisma.
• Utility libraries in /src/lib: db client, Redis client, helpers.
• uploads directory holds user CSVs.
README Insights
• Describes tech stack, features (CSV management, chat, visualizations), prerequisites, setup steps, API routes, env vars.
• Architecture is monolithic Next.js with integrated API layer, Prisma ORM, local Redis, and external LLM calls to Ollama.
a. Main Components
• User’s Browser (React UI)
• Next.js Server (handles SSR/SSG, routing, API endpoints)
• File Storage (local filesystem: /uploads)
• SQLite Database (persistent storage via Prisma)
• Redis Cache
• Local LLM Service (Ollama)
• Docker Compose (orchestration)
b. Relationships & Data Flows
1. User → Browser: interacts with React UI (pages, chat interface, upload form, visualization panel).
2. Browser → Next.js API: HTTP calls to /api/upload, /api/chat, /api/chat/messages, /api/visualization.
3. /api/upload → saves CSV to local filesystem & writes metadata to SQLite via Prisma.
4. /api/chat → retrieves chat history from SQLite, checks/sets cache in Redis, composes prompt, calls Ollama API, returns LLM response.
5. /api/chat/messages → reads/writes message records in SQLite.
6. /api/visualization → queries processed data (from CSV stored or in-memory), returns chart data to frontend.
7. Next.js ORM layer (Prisma client) ↔ SQLite DB for persistent data.
8. Next.js Redis client ↔ Redis for caching frequent queries or LLM responses.
9. Next.js → Ollama (HTTP) for local LLM inference.
c. Architectural Patterns & Principles
• Layered architecture: Presentation (React), API/Business Logic (Next.js), Data Access (Prisma), Persistence (SQLite/Redis).
• Separation of concerns: file storage vs. structured data in DB; caching layer to improve performance.
• Monolithic service containerized for easy local deployment via Docker Compose.
d. Key Technologies & Frameworks
• Next.js 13+ (App Router, Server Components)
• React + Tailwind CSS
• Prisma ORM → SQLite
• Redis (node-redis)
• Ollama local LLM via REST API
• Docker & Docker Compose