How zebangeth/campuscycle works
Main Components
A. Frontend Layer (Vue.js Application):
• Home/Search Interface
• Product Management (Add/Edit Listings)
• User Profile Management
• Authentication Views
• TypeScript integration and Vite build system
B. Backend Layer (Node.js/Express):
• Main API groups based on the routes:
• User Management (/userRoutes)
• Listing Management (/listingRoutes)
• Category Management (/categoryRoutes)
• Admin Operations (/adminRoutes)
• Search Functionality (/searchRoutes)
• Wishlist Management (/wishlistRoutes)
• Middleware layer showing:
• Authentication Middleware
• Admin Authentication
• Request Processing
C. Database Layer:
• MongoDB instance with main collections based on models:
• Users
• Listings
• Categories
• Admins
• Wishlists
D. External Services:
• GitLab OIDC Authentication Service
• Image Storage Service (implied by the structure)
Architecture Pattern Representation
A clear three-tier architecture:
[Client Tier (Vue.js)] ←→ [Application Tier (Express)] ←→ [Data Tier (MongoDB)]
Infrastructure Components
Containers and orchestration:
• Docker containers (show frontend and backend containers)
• Kubernetes cluster components:
• Frontend deployment/service
• Backend deployment/service
• MongoDB deployment/service
Specific Design Elements
• Rectangles: Main components (Frontend, Backend, Database)
• Hexagons: External services
• Rounded rectangles: API endpoints groupings
• Blue: Frontend components
• Green: Backend services
• Yellow: Database components
• Gray: External services
• Red: Security/Authentication components
Key Flows to Highlight
A. Authentication Flow:
User → Frontend → GitLab OIDC → Backend → Database
B. Listing Management Flow:
User → Frontend → Backend (Auth Middleware) → Database
C. Search Flow:
User → Frontend → Backend (Search Routes) → Database → Results