How ikrambagban/itranscoder works
Project type and purpose
• This is a full-stack, multi-deployment pipeline monorepo. It includes:
• A React web frontend for file upload and progress tracking (apps/web)
• A Node.js “backend” API service (apps/backend) that accepts uploads, schedules jobs, and reports status
• A containerized worker service (apps/container) that executes processing jobs in Docker
• A serverless AWS CDK stack and Lambda functions (apps/serverless) for infra provisioning and/or alternative job execution
• Shared libraries and utilities (packages/cloud-services-manager, packages/ui, etc.) to manage ECS, queues, Redis, UI components, configs
• CI/CD pipelines and Dockerfiles for building and deploying all components
File structure
• Top-level “apps” folder holds each deployable service: web, backend, container, serverless
• “packages” holds cross-cutting libraries: cloud-services-manager (ECS/Queue/Redis), UI components, ESLint/TS configs
• Dockerfiles and GitHub Actions workflows define container builds and deployment steps
• Mono-repo orchestrated by pnpm workspaces and Turborepo (pnpm-workspace.yaml, turbo.json)
Main components
A. User & Browser (Frontend)
• React SPA (apps/web)
• Responsible for file selection, upload, and polling for status
B. API Service (Backend)
• Node.js REST API (apps/backend)
• Endpoints: upload, status, control
• Uses helper modules for Docker orchestration and retry logic
C. Processing Worker (Container Service)
• Docker image (apps/container)
• Runs jobs scheduled by the backend
• Reports results/status back (e.g., via a message queue or Redis)
D. Serverless Infra / Lambda
• AWS CDK Stack (apps/serverless/lib/serverless-stack.ts)
• Lambda functions (apps/serverless/lambda) for optional or alternative task execution
• Might serve as a fallback or for asynchronous event handling (e.g., S3 triggers)
E. Shared Infrastructure Services
• Message queue (e.g., SQS or RabbitMQ), Redis cache
• ECS cluster (for Docker tasks)
• S3 or object storage (if relevant for storing uploaded files)
F. Shared Libraries
• cloud-services-manager (manages ECS tasks, queues, Redis)
• ui package for consistent styling / components
Relationships and data flows
1. User → Frontend: initiates file upload
2. Frontend → Backend API: POST /upload
3. Backend → cloud-services-manager → Queue or ECS: enqueue or launch container task
4. Container Worker (Docker) → processes file → writes status to Redis or sends messages to queue
5. Backend polls Redis or subscribes to queue → updates internal job status
6. Frontend polls Backend: GET /status → renders progress bar or final result
7. (Optional) Lambda functions handle asynchronous events (e.g., file processed notifications)
Architectural patterns and design principles
• Microservices / Modularization: each deployable resides in its own directory and Dockerfile or CDK stack
• Polyglot Deployment Options: container-based vs. serverless
• Shared Libraries: avoid code duplication via pnpm workspaces
• CI/CD Driven: GitHub Actions workflows build and deploy each component independently
• Infrastructure as Code: AWS CDK defines serverless stack
Elements
• User-facing components (blue)
• Compute services (green)
• Infrastructure (orange)
• Shared libraries/config (gray)