How arifuzzaman31/ryserve-node works
Detailed Component Breakdown
a) API Routes (3 main routes):
• Admin Routes (/admin)
• Auth Routes (/auth)
• User Routes (/user)
b) Controller Layer (Show two main sections):
• Frontend Controllers
• Auth
• Booking
• SubassetComp
• WishList
• Backend Controllers
• Business
• Asset/Subasset
• Booking
• Dashboard
• Role Management
• Table Management
c) Service Layer:
• Authentication Service
• Owner Service
• User Service
d) Data Layer:
• Prisma ORM
• PostgreSQL Database
Interaction Flows
• Client → API Routes
• Routes → Controllers
• Controllers → Services
• Services → Prisma ORM
• Prisma → PostgreSQL
Middleware Layer (Horizontal)
• AdminMiddleware as a cross-cutting concern
• Authentication/authorization flow
Additional Elements
a) Environment Configuration:
• .env configuration influence
• Deployment workflow (.github/workflows)
b) Helper Utilities:
• Helper functions as a utility layer
Specific Considerations:
Database Schema
• A simplified view of the Prisma schema showing key entities:
• Users
• Assets/Subassets
• Bookings
• Amenities
• Tables
• Business
Authentication Flow
• Auth flow separately
• Token-based authentication process
Booking System
• Booking workflow
• Interaction between frontend and backend controllers