How uday-4083/evolvai works
Main Components
• Client (Browser / Mobile)
• Frontend Next.js App Router (app/ directory pages & layouts)
• UI Component Library (Shadcn UI + Tailwind CSS in components/ui/)
• Authentication Service (Clerk)
• API Layer
– Next.js API Routes (app/api/inngest/route.js, other /api endpoints)
– Server Actions (actions/*.js)
• Business Logic & Utilities (app/lib/, lib/, hooks/)
• Background Job Processor (Inngest functions in lib/inngest/, triggered via API)
• Database (Neon DB Postgres via Prisma in prisma/schema.prisma + prisma client)
• AI Service (Google Gemini API)
• CDN / Static Assets (public/, globals.css)
• Hosting / Orchestration (Vercel serverless functions, Inngest dev/prod endpoints)
Relationships & Data Flows
a. User → Frontend pages (SSR/Server Components) → Server Actions or API calls
b. Frontend ↔ Clerk SDK (for sign‑in, sign‑up, session tokens)
c. API Routes & Server Actions → Business Logic in lib/helper.js, lib/utils.js → Prisma Client → Neon DB
d. API Routes → Inngest (enqueue background jobs like AI‑driven resume/cover‑letter generation)
e. Inngest Worker Functions → Prisma → Neon DB and/or Gemini API calls → update DB → trigger notifications or status updates
f. Frontend polls or subscribes to job status via Next.js API or using Inngest webhook callbacks
g. Frontend → Gemini API (via backend proxy in Server Actions or API Routes) for AI content generation
Architectural Patterns & Principles
– Full‑Stack Monorepo: React + Next.js (app router) tightly coupled with API and server‑side code.
– Server Components & Client Components: /app layouts and pages handle data fetching server‑side, UI components are client‑side.
– API Routes for both synchronous (CRUD) and asynchronous (Inngest jobs) operations.
– Background Job Pattern: decouple heavy AI tasks via Inngest workflows.
– Authentication Middleware: Clerk integration via middleware.js and app/(auth) routes.
– Database Layer: Prisma ORM abstracts Postgres schema and migrations.
Relevant Technologies to Call Out
– Next.js 15 (App Router, Server & Client Components)
– React 18 + Shadcn UI + Tailwind CSS
– Clerk for authentication
– Prisma ORM + Neon DB (Postgres)
– Inngest for background jobs
– Google Generative AI (Gemini) for AI features
– Vercel for Hosting & Serverless Functions
Things to Emphasize
– The separation of concerns between UI, API, jobs, and data storage
– How Clerk sits between user and Next.js for auth
– The two pathways for AI tasks: synchronous (via Server Action) vs asynchronous (via Inngest)
– Prisma as single source of truth for data model and migrations
– The flow of environment‑driven configuration (env vars for Clerk, Gemini, Database)
Putting It All Together