How shrutika-panchal/streamingapp works
Project type and purpose
• This is a full-stack, cloud-native, microservices-based “Collaborative Streaming” application.
• The frontend is a React single-page app. The backend consists of four Node.js/Express microservices (AuthService, ChatService, CoreAPIService, StreamingService).
• It uses MongoDB for persistence, AWS S3 for video storage, Docker for containerization, Kubernetes (with Helm charts) for orchestration, Terraform for infra provisioning, Jenkins and Argo CD for CI/CD.
File structure
• backend/ contains four subfolders:
• authService – user authentication, JWT issuance, user model
• chatService – real-time chat API (likely via WebSockets or REST)
• coreAPIService – aggregates or proxies calls to other services
• streamingService – serves media streams from AWS S3
• frontend/ is a Create React App; package.json, public/, src/
• k8s/ defines Namespaces, Deployments, Services, Secrets for auth, streaming, database (Mongo), frontend. Also a Helm chart under k8s/streamingapp.
• terraform/ provisions the underlying infrastructure (e.g., cloud resources, VPC, EKS cluster, or managed MongoDB).
• Argo CD app manifest and Jenkinsfile automate build & deployment pipelines.
README
• Confirms streaming focus and lists AuthService environment variables (Mongo URI, JWT secret, AWS credentials).
Elements
• Clear labels for each component (e.g., “AuthService (Node.js)”).
• Cluster boundary: Kubernetes
• Annotation of ports (e.g., 3001 for AuthService) and protocols (HTTP, WebSocket, S3).