How gay22222/ai-matching-webapp works
Project type and purpose
• This is a full-stack web application (“AI Matching Webapp”) consisting of:
• frontend/: a Next.js client
• matching-backend/: a Node.js (Express) API server with Prisma, AI embedding pipelines, WebSocket messaging
• Purpose: a matchmaking/chat app using AI embeddings (Weaviate) to recommend user matches, real-time chat, notifications, and profile management.
File structure
• Top-level: frontend/ + matching-backend/
• frontend/:
• Next.js App Router under src/app, organized by route (discover, matches, message/[matchId], notifications, profile, settings)
• Components/hooks/context/redux slices in src/…
• Configuration: Dockerfile, docker-compose.yml, ESLint, Tailwind, postcss, next.config
• Public assets and environment files
• matching-backend/:
• Express structure: src/routes → controllers → services → repository → Prisma client
• AI pipelines under src/ai (convert/generate user JSON, embedServer, embedding, pipeline, user_data storage)
• Weaviate integration in src/ai/weaviate
• WebSocket helpers in src/utils/socketHelpers and src/sockets
• File uploads persisted under uploads/
• Prisma schema and seed scripts under src/prisma
• Scheduler/cron jobs in src/utils/scheduler
• Configuration: Dockerfile, docker-compose.yml, nodemon, requirements.txt
README for additional insights
• Confirms Next.js in frontend, Express/Prisma in backend
• Mentions Docker support
• Breakdown of responsibilities: AI embeddings, notifications/socket.io, chat, matchmaking logic, user management
Elements
• Clear component labels (e.g., Next.js Client, Express API, Prisma DB, Weaviate)
• UI components (blue rectangles)
• API/Services (green)
Final recommendations
• Don’t forget the Prisma seed & migration step as part of the DB lifecycle
• Where environment variables and configs (Docker Compose) tie components together