Chaudhari Law Publishers

Core System Architecture The application follows a Jamstack‑style architecture where the frontend (React + TailwindCSS) is rendered by Next.js and API routes are deployed as serverless functions on Vercel. Each route lives under app/api/* and uses NextResponse for standardized JSON envelopes. Database interactions are abstracted through Mongoose models (Book, Category, Subject, Order, User, Author, Publisher) with a shared connection pool created by dbConnect(). Text indexes on title, author, SKU, description, and keywords enable fast full‑text search without an external search engine.

Authentication & Session Guardrails User authentication is handled by NextAuth.js using a credentials provider. Sessions are stored in HTTP‑only cookies and validated by a global middleware.ts that redirects unauthenticated requests. Environment variables (NEXTAUTH_SECRET, NEXTAUTH_URL) are required for token signing and callback URLs. Admin credentials are pre‑seeded (chaudharilawpublishers@gmail.com).

GET /api/auth/captcha provides a public captcha challenge, while protected routes such as GET /api/user/profile, GET /api/user/cart, PUT /api/user/cart, GET /api/user/wishlist, and address management endpoints enforce session checks. Payload schemas are defined in the API guide and validated with Zod‑style checks before processing.

Data Flow & Execution Client requests hit the Next.js API route, the handler parses JSON, validates against the schema, and invokes Mongoose service functions. The service layer performs CRUD on the chaudhari_law database, leveraging MongoDB's atomic operators for cart updates and order creation. Responses are wrapped in a consistent envelope ({ success: true, data: … }) and sent via NextResponse.json(). Rate limiting and error handling policies are documented in the API guide but enforced centrally via middleware.

Build & Deployment Topology The codebase is TypeScript‑first, linted with ESLint, and compiled by the Next.js build pipeline. Deployments target Vercel's edge network, providing automatic scaling for API routes. MongoDB Atlas handles data persistence with built‑in backups and geo‑replication, ensuring high availability for the publishing catalog.