Backing Tracks NestJS

Project Description

Check the frontend repository for general project description frontend repository.

TODOs

see project TODOs

App Stack

• NestJS
• TypeORM
• Postgres
• BullMQ (queue system built on top of Redis)
• ffmpeg, yt-dlp

Infra Stack

• As of now, the apps are ran on AWS as ECS tasks on an EC2.
• CI/CD with CodePipeline, CodeBuild, ECR.
• Infrastructure is as code - AWS CDK.
• For v2, will go more serverless & event driven & cheaper* and will actually make the app scalable** - ApiGW, Lambda, SQS, EventBridge, DynamoDB etc.
• and 5-10 years from now, I will probably just go back to something like v1 & and keep it super simple and just run all the containers on some dirt cheap VPS. So I need to keep this in mind.

Folder Structure

This is a NestJS monorepo:

• apps/api - HTTP REST API. All the standard CRUD stuff. Authentication, mTLS, and few other things, are already handled before a request lands here.
• apps/ytdl - TCP microservice & job processor. Ytdl stands for YouTube DownLoader, and this is what this service is mostly about. It is based on the yt-dlp library for downloading tracks from YouTube, and converting them to mp3 using ffmpeg. And since it already has ffmpeg as a dependancy, we also use it for a couple strictly ffmpeg related tasks.
• libs/database - all database related stuff: entity/schema definitions, repositories.
• libs/job-queue - all BullMQ related stuff. Mainly a thin wrapper for publishing youtube download jobs, some common read operations on the queue, and some queue event listeners.
• libs - in general, a lot of (core) code lives there.

Installation

TODO