Being new to node js magic world, i'm wondering how does a web application's setup look like on a real production server? So far all tutorials, create the js file that is started from a console...and that's it. Anyone has created a real world web app that uses node js in the back end? Can you please describe how is it setup, and how reliable this infrastructure is ? I'm coming from the asp.net and php world that require heavy web servers...and can't have a clear idea about node stuff.


3 Answers 3


I work on a node.js web application that is not yet in production, but we do run a development server setup similarly to how I would setup production.

It's a Linux server (CentOS specifically, but any distro would do) with a service account dedicated for running the web app. Deployment is as simple as SCP'ing the tarball file up to the server and running:

$ npm stop <app name>
$ npm install ./<app name>-<version>.tgz
$ npm start <app name>

npm allows for life cycle scripts to be setup via package.json which is how npm stop and npm start are implemented. By default, npm start calls node server.js if there is a server.js in the top-level directory. You can define your own start script easily via package.json.

We use the daemon module when starting up via npm start in order to run the app in the background, totally disconnected, with output redirected to a log file. Starting directly via server.js, however, skips the daemon step so I have an interactive terminal in development.

Since we use npm for packaging and installation, the code ends up living under $HOME/node_modules/. And again, this runs under a dedicated user account, so I know exactly what modules are and are not available at runtime.

In order to leverage multiple CPU's, the server.js script will fork a worker (via the cluster module) for each CPU and monitor them for death. If a worker dies, the master process restarts it. There are modules out there to kick off your app and auto-restart if it dies, however, given that our master does no work except for baby sitting the workers, I don't bother watching the master. The game of "who watches the watchers" could go on infinitely.

When going to production, there are only three more elements to build out, which we have not done yet:

  1. Load balancing, which is not part of the app itself and has nothing to do with node.js
  2. An init script to start and stop the service when the server box is rebooted.
  3. When shutting down the service to install a new release, we need to remove it from the load balancer pool and then put it back in.

Use a Platform as a Service.

I've successfully deployed to Heroku and Jit.su. Nodester seems cool, and I've used Azure for .NET things and if Node.js is equally good then that is a good option as well.

If you want to host a node app on your own server you could just run node app.js on your server.

  • 1
    Can you please explain why did you choose to deploy in a cloud service? Is it for security, complexity or maintenance/evolution of the solution deployed? Also, any idea about node apps security? Hacking is a kids game nowadays :s
    – joe
    Apr 4, 2013 at 19:25
  • This is a perfectly reasonable answer, not sure why it was downvoted. Although the question didn't specifically ask about PaaS, it's still common enough that people aren't aware of PaaS providers.
    – dsw88
    Sep 17, 2013 at 19:25

I have came across the similar asignment where I asked to implement or create three different modules.

  1. Web application
  2. REST application
  3. Node

All my web application requests are pointing to REST module which is purely Spring web service implementation. This is before node.js coming in to picture. Later I asked to add node layer in between web and REST module so that all my web applications request should route through node module and node will hand it over to REST module and vice versa. This is because looking at the business need and some specific requirement.

So my web application is having all static html implementation which are calling node.js module through jquery ajax call and on success html dom elements are filled up with some values.

Lets take an example I have a button click event on which jquery ajax call should be called to node application. For this node application must be in running state. To run node.js application use following command.

$ node index.js

Where index.js is my main starting point for node module which has some url e.g. getContactDetails

$(document).on("click", "#btnClick", function(event) {
type : 'POST', 
url : "http://nodeserver:port/appurl", 
dataType :"json", 
data : JSON.stringify(someJSON), 
contentType : "application/json;charset=utf-8", 
success : function(data) {
    /*Some code*/},
error :function(data) {
    /*Some code*/}

Inside node I am giving call to REST module like below

            url : restUrl,
            method : "POST",
            headers : { "Content-Type" : "application/json","pubKey":composeJSON},
            body : JSON.stringify(tmp.body)
        function (error, res, body) {
            indexresponseBody = JSON.stringify(JSON.parse(body).message);
    res.writeHead(200, {'content-type':'text/html'});
  • 1
    He want's to know more about the hosting architecture (like proxy with multiple node instances behind), not the application architecture itself. Sep 17, 2013 at 16:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.