There are a lot of postings around Node.js offering code snippets pushing stock data and more. Unfortunately, few of these postings offer thoughts around resilence, and deployment within an enterprise DMZ supporting resilence.
Lets start by consider the simple scenario of a pricing engine that provides a continues stream of prices, which we want to deliver to a HTML client via a Node.js server. For this posting, lets ignore the issue of the pricing engine failing, and concentrate on failure of the Node.js server, and disconnection of the HTML client. If in the simple scenario we had the Node.js server connect to the pricing engine, on a HTML client connecting to the Node.js server, if the Node.js server died, we would loose any data the pricing engine sent between the time the Node.js crashed, and the time the client reconnected to a new Node.js server, or the original re-started Node.js server. We’ll ignore expired prices for this posting as well
Read more...