CODEWITHSUNDEEP
javascriptnode.js
Tyler Gillies
Tyler Gillies

Reputation: 1907

nodejs without stopping

Is there a way I can make nodejs reload everytime it serves a page?

I want to do this during the dev cycle so I can avoid having to shutdown & startup on each code change?

Upvotes: 6

Views: 4938

Answers (5)

nalply
nalply

Reputation: 28787

Edit: Try nodules and their require.reloadable() function.

My former answer was about why not to reload the process of Node.js and does not really apply here. But I think it is still important, so I leave it here.

Node.js is evented IO and crafted specifically to avoid multiple threads or processes. The famous C10k problem asks how to serve 10 thousand clients simultaneously. This is where threads don't work very well. Node.js can serve 10 thousand clients with only one thread. If you were to restart Node.js each time you would severely cripple Node.js.

What does evented IO mean?

To take your example: serving a page. Each time Node.js is about to serve a page, a callback is called by the event loop. The event loop is inherent to each Node.js application and starts running after initializations have completed. Node.js on the server-side works exactly like client-side Javascript in the browser. Whenever an event (mouse-click, timeout, etc.) happens, a callback - an event handler - is called.

And on the server side? Let's have a look at a simple HTTP server (source code example taken from Node.js documentation)

var http = require('http');

http.createServer(function (request, response) {
  response.writeHead(200, {'Content-Type': 'text/plain'});
  response.end('Hello World\n');
}).listen(8124);

console.log('Server running at http://127.0.0.1:8124/');

This first loads the http module, then creates an HTTP server and tells it to invoke the inner function starting with function (request, response) every time an HTTP request comes in, then makes the server listen to port 8124. This completes almost immediately so that console.log will be executed thereafter.

Now Node.js event loop takes over. The application does not end but waits for requests. And voilà each request is answered with Hello World\n.

In a summary, don't restart Node.js, but let its event loop decide when your code has to be run.

Upvotes: 9

alessioalex
alessioalex

Reputation: 63683

There are many apps for doing this, but I think the best is Cluster, since you have 0 downtime for your server. You can also set multiple workers with it or manually start/stop/restart/show stats with the cli REPL functionality.

Upvotes: 0

Tyler Gillies
Tyler Gillies

Reputation: 1907

Found Nodemon, exactly what I wanted: https://github.com/remy/nodemon

Upvotes: 6

wdavidw
wdavidw

Reputation: 161

I personnaly use spark2 (the fork) and will switch to cluster as soon as i found the time to test it. Among other things, those 2 will listen to file changes and reload the server when appropriate, which seems to be what you're looking for.

Upvotes: 0

Tor Valamo
Tor Valamo

Reputation: 33789

No. Node.js should always run. I think you may have misunderstood the concept of nodejs. In order for nodejs to serve pages, it has to be its own server. Once you start a server instance and start listening on ports, it will run until you close it.

Is it possible that you've called a function to close the server instead of just closing a given stream?

Upvotes: -3

Related Questions