mahi8026/health_care_e-commerce

1. System Purpose and Entrypoints

Mediport BD is a Bangladesh-focused B2B/B2C medical-equipment commerce system. The main application is nested under health-care/; outer-root files are primarily repository administration. Runtime entrypoints are the Next.js App Router frontend at health-care/src/app/layout.jsx and health-care/src/app/page.jsx, plus the Express API at health-care/backend/src/server.js.

2. Frontend Delivery Layer

Next.js 16 / React 19 renders public commerce, customer, B2B, and admin experiences. File-based routes separate major surfaces: catalog/detail pages in health-care/src/app/products/page.jsx and health-care/src/app/products/[...id]/page.jsx; checkout in health-care/src/app/checkout/page.jsx; privileged operations in health-care/src/app/admin/layout.jsx. Client state crosses UI boundaries through contexts, notably health-care/src/context/AuthContext.jsx, health-care/src/context/CartContext.jsx, and health-care/src/context/WishlistContext.jsx.

3. API Boundary and Request Pipeline

The Express service exposes domain-specific REST route modules, which dispatch to controllers and services, then Mongoose models. Core routing domains include health-care/backend/src/routes/authRoutes.js, health-care/backend/src/routes/productRoutes.js, and health-care/backend/src/routes/orderRoutes.js. Cross-cutting middleware establishes authentication, validation, caching, throttling, health checks, request correlation, and error handling; central examples are health-care/backend/src/middleware/auth.js, health-care/backend/src/middleware/cache.js, and health-care/backend/src/middleware/errorHandler.js.

4. Commerce and Fulfillment Domain

Catalog, category, manufacturer, cart, order, payment, coupon, review, return, quote, and B2B data are persisted as MongoDB/Mongoose documents. The commercial center is represented by health-care/backend/src/models/Product.js, health-care/backend/src/models/Cart.js, and health-care/backend/src/models/Order.js. Order processing is separated into service logic in health-care/backend/src/services/orderService.js; pricing supports standard, flash-deal, and B2B behavior through health-care/backend/src/services/pricingService.js and health-care/backend/src/services/flashDealPricing.js.

5. Identity, Customer Programs, and Operations

Authentication supports JWT and Google OAuth through Passport configuration, with 2FA and token blacklisting services. Relevant boundaries are health-care/backend/src/config/passport.js, health-care/backend/src/services/twoFactorService.js, and health-care/backend/src/services/tokenBlacklist.js. Customer retention and enterprise workflows include loyalty, B2B terms/quotes, marketing, notifications, and WhatsApp: health-care/backend/src/services/loyaltyService.js, health-care/backend/src/controllers/b2bController.js, and health-care/backend/src/services/whatsappService.js.

6. Integrations, Async Automation, and Observability

MongoDB Atlas is the system of record; Redis provides API/rate-limit caching with an in-memory fallback via health-care/backend/src/services/redisCache.js and health-care/backend/src/services/cacheService.js. Cloudinary is the media CDN/upload target (health-care/backend/src/services/uploadService.js). External delivery and engagement paths include email, SMS, Steadfast shipping, WhatsApp, and n8n webhooks, represented by health-care/backend/src/services/emailService.js, health-care/backend/src/services/steadfastService.js, and health-care/backend/src/services/n8nWebhookService.js. n8n workflow definitions live in health-care/automation/workflows/.

7. SEO, Edge Functions, and Deployment

The frontend produces search and merchant-facing output through dynamic sitemap, robots, merchant-feed, and OG routes: health-care/src/app/sitemap.xml/route.js, health-care/src/app/robots.js, and health-care/src/app/api/merchant-feed/route.js. It also includes PWA assets under health-care/public/sw.js. Vercel hosts the frontend (health-care/vercel.json), while the Express backend is deployable to Render (health-care/backend/render.yaml) and contains Railway configuration. Sentry is configured separately for browser, edge, server, and API runtimes.