How fatihege/rival-music works
Main Components
a. Client (Next.js/React) – SSR web application serving UI and static assets
b. API Server (Express.js/Node.js) – RESTful endpoints, business logic, controllers/models
c. Database (MongoDB) – persistent storage of users, tracks, playlists, artists, etc.
d. Cache (Redis) – in-memory store for session data, caching frequently accessed queries
e. Search Engine (MiniSearch) – full-text search index embedded in the API layer
f. External Services
• Mailer (SMTP via server/lib/mailer) for activation, password reset
• File storage (local filesystem or cloud) for uploaded audio via multer
g. Docker Compose – orchestration of containers for the above components
Relationships & Data Flows
• User’s browser ⇄ Next.js server:
– HTTP(S) requests for pages, API calls from client-side React components
– Server-Side Rendering of pages on initial load
• Next.js server → API server:
– Calls REST routes (e.g., /api/track, /api/user) defined in server/routes
• API server → MongoDB:
– CRUD via Mongoose models (server/models/*.js)
• API server ↔ Redis:
– Read/write cache for hot data (sessions, recent searches) via server/lib/redis.js
• API server → MiniSearch:
– Build and query in-memory index for fast full-text search of tracks, artists
• API server → Mail Service & File Storage:
– Send emails (server/lib/mailer.js), store/delete uploaded audio files (server/lib/multer.js)
Architectural Patterns & Principles
• SSR Pattern (Next.js) – improves SEO and initial-load performance
• MVC-style API – controllers (server/controllers/*.js), models (server/models/*.js), routes
• Middleware Pipeline – auth, admin checks (server/middlewares/*.js), input validation
• Caching Layer – Redis to reduce DB load and speed up responses
• Modular Frontend – React contexts, reusable components (client/src/components, client/src/contexts)
• Containerization – each service (client, server, MongoDB, Redis) runs in its own Docker container