Scalable event-driven applications with NestJS
summary
NestJS + Redis queues run in Docker with Make targets (make start, make monitor, start Step 1/Step 2) and a channel monitor that collects queue metrics so you can watch jobs waiting. Demo simulates a 3x traffic spike, then applies two fixes: split critical work onto a dedicated trade queue with zero waiting jobs and raise the default queue worker count to 3. Also covers send vs emit semantics, messagePattern vs eventPattern, TypeScript DI bootstrap, and that the changes restore steady processing.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:48NestJS for scalable dev
- 5:39Monoliths vs microservices vs event-driven
- 7:06Event-driven with NestJS
- 9:57Demo setup
- 11:22Monitoring event queues
- 12:03Handling traffic spikes
- 13:29Scaling with NestJS
- 15:35Recap and next steps
related talks
22mTaming reactive node.js: Stream-oriented architecture with NestJS
31mDeveloping Microservices with NestJS
01h 08mDeep Dive Into NestJS
38mBuild modern and scalable Node.js Web Applications with Nest
22mRapidly Developing Microservices with Node js and Docker
26mBuilding a platform: NestJS from the ground up
22mBuilding Automation Systems with NestJS
27mA Practical Introduction to WebSockets