Event Management Application

Core System Architecture The application follows a serverless micro‑service style where the Next.js App Router serves both the UI and lightweight API routes. UI components run as React Server Components or Client Components as needed, while business logic is encapsulated in Server Actions that directly interact with the MongoDB database using Mongoose models (e.g., Category, Event, Order, User). This eliminates the need for a traditional REST layer and reduces client‑side JavaScript payload.

Data Flow & Execution User interactions (e.g., creating an event, purchasing a ticket) trigger Server Actions which perform type‑safe CRUD operations on MongoDB. For payments, the checkoutOrder action calls the /api/orders endpoint to create a Razorpay order, then redirects the user to Razorpay’s checkout UI. Upon successful payment, Razorpay sends a webhook to /api/webhook/razorpay (not shown) which updates the order status in the database.

Security Guardrails Authentication is handled by Clerk, with user sessions managed via secure HTTP‑only cookies. Svix forwards Clerk webhook events to the internal /api/webhook/clerk route, ensuring the local user records stay in sync. Environment variables protect sensitive keys (RAZORPAY_KEY_ID, RAZORPAY_SECRET). All server‑side code runs in a Node.js runtime isolated from the client, minimizing attack surface.

Build & Deployment Topology The project is deployed on a serverless platform (e.g., Vercel) where each API route and Server Action scales automatically. Static assets (Tailwind CSS, Shadcn UI components) are bundled at build time, while media uploads are off‑loaded to Uploadthing, which returns CDN URLs for immediate use in the UI. The next-themes package provides seamless dark/light mode toggling without additional server load.