Skip to content

Latest commit

 

History

History
19 lines (14 loc) · 1.59 KB

CONCURRENCY.md

File metadata and controls

19 lines (14 loc) · 1.59 KB

Quick links : Home - Part 1 - Part 2 - Part 3 - Part 4 - Part 5


Part 5 - Codebase - Dependencies - Config - Backing services - Build, release, run - Processes - Port binding - Concurrency - Disposability - Dev/prod parity - Logs - Admin processes


Scale out via the process model

Node-RED runs as a single process, where the main application runs on the main Node.js execution thread. There is no inbuilt scale out mechanism in Node-RED.

The way concurrency is handled is by running additional instances of the node-RED application and routing traffic between the instances. In a cloud environment this is usually by deploying additional instances of the application container


Part 5 - Codebase - Dependencies - Config - Backing services - Build, release, run - Processes - Port binding - Concurrency - Disposability - Dev/prod parity - Logs - Admin processes


Quick links : Home - Part 1 - Part 2 - Part 3 - Part 4 - Part 5