How to prepare a distributed nodejs application

on YouTube ↗16m

" summary

A Node.js monolith of about 32k LOC and an npm shrinkwrap near 1k lines gets split into services that register via mdns today but fall back to additional engines (SLP work in progress) because of mdns issues on Linux. Services declare hard vs soft dependencies so dependents auto-start and auto-stop, retries and load balancing happen automatically, transactions use a redis (or Kestrel) working-queue for safe retries, remote deps live in package.json, and the system runs on AWS.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:56AUTOMATIC SOFTWARE TESTING
3. 1:10SERVER
4. 2:46DISTRIBUTED APPLICATIONS
5. 12:46STREAMS VS TRANSACTIONS
6. 14:09HOW IT WORKS

" related talks

• 01mHow npm split a monolith and lived to tell the taleLaurie Voss · Fluent 2016
• 44mMicroservices - the lean way (NodeJS)Bruno Bossola · Codemotion Amsterdam 2016
• 52mMicroservices the Lean Way NodeJSBruno Bossola · Codemotion Rome 2016
• 40mDeploying node.js at scaleLuca Maraschi · Codemotion Amsterdam 2016
• 27mProgressive Microservices with NodeJSShashank Sharma · Developer Summit 2020
• 48mMicroservices with NodeJSRico Fritzsche · code.talks 2017
• 43mPatterns for Reactive node.js MicroservicesAlexander Thiel · code.talks 2017
• 23mBuilding Distributed Systems with Node.jsJames Simpson · Nordic.js 2019