All Projects
Full StackCase Study·89% Match

Music Streaming — 3-Tier MERN on AWS EKS

3-tier microservice music streaming platform. Frontend: React/Vite + Tailwind CSS + Context API. Backend: three TypeScript/Node.js/Express services (userService, adminService, songService) backed by MongoDB and NeonDB (PostgreSQL). Redis caching, Cloudinary for audio/image assets, JWT authentication. Docker Compose for local dev; Jenkins CI/CD pipeline (SonarQube, OWASP, Trivy) deploys to AWS EKS via Kubernetes manifests.

ReactNode.jsExpressMongoDBPostgreSQLDockerNginx
Production3-TierArchitecture3 ServicesMicroservicesEKSKubernetesNeonDBPostgreSQL★ Featured
3-Tier
Architecture
3 Services
Microservices
EKS
Kubernetes
NeonDB
PostgreSQL
🔴 The Problem
▸

Monolithic music apps can't scale individual services independently

▸

Local dev environment differed significantly from production Kubernetes deployment

✅ The Solution
▸

3 TypeScript/Node.js microservices (user, admin, song) behind Nginx; Docker Compose for local dev; Jenkins CI + EKS for production

▸

Cloudinary stores audio/image assets; Redis caches session tokens; NeonDB handles relational data

📈 Impact & Results
▸

Services scale independently: song service can handle 10× load without touching user auth

▸

JWT + Redis session management delivers sub-10ms auth checks

▸

Jenkins pipeline runs SonarQube + OWASP + Trivy before any EKS deployment

Full Tech Stack
ReactNode.jsExpressMongoDBPostgreSQLDockerNginxRedisKubernetesAWS EKSJenkinsSonarQube

More Projects

Agentic AI
Disaster Response AI Copilot
Machine Learning
Crypto Trade Prediction
Machine Learning
Heart Disease Prediction with Generative AI
Machine Learning
Car Price Prediction — MLflow + Kafka + Debezium
Interested in working together?
Let's build something impactful.