How mbrizic/ratethegame works
Main System Components
A. Client Layer
• Server-Side Rendered UI (highlight that there's no client-side JavaScript)
• Main UI components structure (/ui directory)
• Pages (login, register, events, sports)
• Components (cards, forms, lists)
• Core UI services (CSS, HTML operators)
B. Application Layer
• Core Services
• Authentication Service
• Cache Service (emphasize in-memory caching of domain models)
• Mail Service
• Analytics Service
• File Service
• Domain Services
• Sports Service
• Events Service
• Users Service
• Notifications Service
• Ratings Service
C. Data Layer
• PostgreSQL Database
• Sequelize ORM
• Domain Models
• Sports
• Events
• Users
• Event Ratings
• User Settings
• User Sport Subscriptions
Key Architectural Patterns to Highlight
• MVC-like pattern:
• Controllers (/server/*/*.controller.ts)
• Models (/database/models)
• Views (/ui/component, /ui/page)
• Caching mechanism:
• Relationship between cached domain models
• Cache boundaries
Specific Elements
• Core Infrastructure
• Error Handling
• Middleware
• Authentication
• Input Validation
• Route Handling
• Business Logic Layer
• Sports Management
• Event Rating System
• User Management
• Notification System
Key flows:
• User request → Server → Cache/Database
• Authentication flow
• Rating submission flow
• Cache invalidation flow
• Notification dispatch flow
Important Notes
Callouts for:
• Cache invalidation complexity
• No client-side JavaScript
• Custom templating engine
• Future recommendation engine integration points
• Potential scaling considerations