Building Distributed Systems with Node.js
summary
Node.js servers use Primus (WS) to add WebSocket multiplayer to a simple drawing app, then HAProxy at :8000 load balances across two app instances and democracy.js pub/sub replicates events so clicks broadcast to all servers. Demo runs on DigitalOcean with four servers, survives single-server failures and rebalances connections, and the team reports outages dropping from two to three per week to two to three in five years. Core claim: small Node code plus democracy.js pub/sub makes a working distributed system.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:01Minimizing Downtime
- 4:40Basic Distributed System
- 5:24Health Checks
- 6:32Application Layer
- 6:54Messaging Layer
- 7:46Democracy Jas
- 8:49Set Up Our Application Layer
- 9:37Node Server
- 10:18Primus Server
- 13:21Add the Load Balancing Layer
- 22:27Recap
related talks
41mDistributed Systems explained with NodeJS
40mDeploying Node : from localhost to the cloud
31mNode.js that's hugely reliable, fast, and scalable
16mHow to prepare a distributed nodejs application
29mWhy would we ever build a distributed computing platform in node?
29mPortable DIstributed Systems Using Node on "Routers"
19mErich Oliveira
18mRealtime HTML5 Multiplayer Games with NodeJS