How dubeyshubham108/tunewave-music-streaming-platform works
Project type and purpose
• This is a full-stack MERN + PostgreSQL microservices music-streaming platform.
• It consists of three Node.js/TypeScript microservices (user service, song service, admin service), a React frontend (user UI + admin dashboard), and a shared PostgreSQL database.
Core architectural components
a. Clients (Web UIs)
• Music Streaming Web App (React)
• Admin Dashboard (React)
b. API Layer
• (Optional) API Gateway or reverse-proxy routing incoming UI/REST calls to the proper service
c. Microservices
• User Service (Express/TypeScript)
• Song Service (Express/TypeScript)
• Admin Service (Express/TypeScript)
d. Data Store
• PostgreSQL instance (single cluster or per-service schemas)
Relationships & data flow
• All UI traffic (user or admin) flows down through the API Gateway (or directly hits each service).
• Each microservice uses its config/db module to connect to PostgreSQL.
• The Admin Service may also call the User and Song services or directly query shared tables for analytics.
Architectural patterns & principles
• Microservices: each service is independently deployable, owns its own routes, controllers, models (see src/model.ts in user service).
• Shared database vs. separate schemas: use one cluster with per-service schemas or logical separation.
• TryCatch wrapper around all controllers for consistent error handling.
• TS → JS build pipeline under dist/ for each service.
Technologies & frameworks
• Node.js + Express + TypeScript
• PostgreSQL (pg library configured in src/config/db.ts)
• React for UIs (not in file tree but implied by MERN)
• tsconfig.json, package.json for build/dependencies