Building Reliable Backend with Node.js
summary
Shows concrete failures and fixes: a 43 seconds out-of-sync = 24 hours downtime on GitHub example, a customer losing $500,000 from a three‑character bug, and a real app built on Firebase plus flaky third‑party APIs. Advocates runtime contracts with extracted Flow/TypeScript types, dependency injection via inversify, GraphQL‑generated types, and Nest as a framework; calls out poor reflect‑metadata and NPM trust issues and reports using VS Code for language‑server tooling.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:57Importance of Reliability
- 4:54Duck Syndrome
- 7:02Assumptions
- 10:30Can We Trust Third Party Api
- 18:52Variance on Flow
- 23:03Dependency Injection
- 37:53About Typescript
- 39:42Language Server Protocol
- 41:25Reflect Metadata in Typescript
related talks
26mWhat's your backend written with? JavaScript?!
08mMonitoring Errors and Slowdowns with a JS Frontend and Node Backend
01h 13mModern Backend for Frontend on Node.js
16mDependency Hell Just Froze Over
46mArchitecture of a Modern Enterprise Node js Application
32mBuilding for Gracious Failure
38mThe Power Of Process Automation
22mAI-powered JavaScript Development