How sesto-dev/next-prisma-tailwind-ecommerce works
Project Type and Purpose
• This is a monorepo hosting a full-stack e-commerce platform, composed of two separate Next.js 14 applications:
• Admin Panel (apps/admin)
• Storefront (apps/storefront)
• Both apps use React Server Components, the App Router, Prisma ORM (PostgreSQL backend), TailwindCSS for styling, and share utility packages under packages/.
High-Level File Structure Analysis
• Root
• Configuration files (.eslintrc.js, bun.lockb, package.json, etc.)
• apps/ – two Next.js apps
• packages/ – shared libraries (mail, oauth, sms, zarinpal, slugify, regex, rng)
• Each app (admin and storefront) contains:
• src/app/ – UI pages and API routes
• src/components/, src/hooks/, src/lib/, src/providers/, src/types/ – logical layers
• prisma/schema.prisma & ORM client wrapper (lib/prisma.ts)
• middleware.ts – authentication (JWT in httpOnly cookies)
• Shared packages implement cross-cutting services (email/SMS sending, OAuth, payment gateway integration, utility functions).
Main Components
a. Frontend & BFF Layers (for each app)
– Next.js App Router (UI pages)
– React Server Components & server actions
– API routes (src/app/api/.../route.ts)
– JWT middleware (auth guard)
b. Data Layer
– Prisma ORM
– PostgreSQL database
– Seed scripts (admin app)
c. Shared Services (external or via packages/)
– Email service (Cloudinary for file uploads, react-email templates, SMTP transport via mail package)
– SMS service (via sms package)
– OAuth providers (Google, Apple via oauth package)
– Payment gateway (Zarinpal package)
d. Deployment Units
– Two separate Vercel (or Docker) deployments for Admin and Storefront
– Monorepo CI/CD pulling from shared root
Relationships and Data Flows
• User → Browser → Next.js UI
• UI → (HTTP) → Next.js API Routes
• API → Prisma client → PostgreSQL (CRUD: products, orders, users, payments, blogs)
• API → External packages → External services (email, SMS, OAuth, payments)
• Middleware intercepts requests → validates JWT → injects X-USER-ID header → downstream handlers
• Shared packages called both by Admin and Storefront servers
Architectural Patterns & Design Principles
• Backend-For-Frontend (each Next.js app serves its own BFF)
• Monorepo modularity (shared packages for DRY code)
• Layered architecture (UI → API → Services → Data)
• Server Components for performance and partial hydration
• Secure cookie-based JWT auth via middleware
Detail & Labels
• API route groups (e.g., /api/products, /api/auth/otp)
• Middleware JWT validation and header injection
• Prisma schema and client instantiation (lib/prisma.ts)