How bhupesh227/e_commerce_multivendor works
Project type and purpose
• This is an Nx-powered monorepo hosting a full-stack e-commerce platform.
• It uses a microservices architecture for the backend (auth, order, product, seller, recommendation, chatting, logger, kafka, etc.), a central API gateway, and three separate Next.js frontends (admin-ui, sellers-ui, users-ui).
• Shared code lives in Nx libs (components, middleware, error‐handler, utils, Prisma/Redis/Stripe wrappers).
File structure
• Top-level “apps” directory: each folder is either a microservice (Node + Express/Koa style) or a Next.js UI.
• “apps/api-gateway” routes client traffic to the various microservices.
• “apps/*-service” are domain services; they each expose a REST or WebSocket interface and use shared libs (Prisma for DB, Redis for caching/messaging, Kafka for event bus).
• “apps/*-ui” are Next.js apps with React components, hooks, and API routes for client side interactions.
• “packages” contains shared UI components, middleware, and utility libraries.
• Prisma schema is at the root, meaning a centralized database or multiple schemas managed from here.
• CI and build configs (.github/workflows, nx.json, tsconfig) confirm an Nx workspace orchestrating builds and dependency graph.
Extra insights from README
• Uses generated build targets per app, and Nx plugins for consistency.
Detail without over-splitting
• Microservice as its own component.
• Shared libraries only once under a “Shared Libraries” block.