By Nathan Tippy, OCI Principal Software Engineer

March 2012


Node has grown very quickly in popularity due to its excellent performance and ease of use.  It introduces event-driven techniques commonly found in desktop applications to the world of hosted server applications.  Google's V8 JavaScript engine is core to the Node framework and the use of JavaScript as the primary language for Node has provided it with a large community of potential developers already familiar with the language.  This low learning curve in addition to its excellent performance has contributed greatly to its fast growth.

What is 'Event-Driven'?

As with most things, "there is nothing new under the sun", so let's look at a real world example.  Many streamlined businesses are way ahead of us when it comes to applying event-driven techniques.  After putting in my order at Starbucks, the cashier informs the barista what to make.  At this point I step aside and wait while the barista makes my drink and the cashier takes the next order.  Once my drink is ready they call my name to come pick it up.  This strategy allows them to service many customers at the same time with one cashier.  Now imagine what would happen if I did not step aside until my drink was complete.  Every customer would have to wait for the full duration of all previous transactions before beginning their own.  This would force them to spend a lot of time standing in line.  The event-driven process enables us to quickly place an order, sit, relax, and do other tasks while we wait to be called.  This also allows Starbucks to maximize profits by minimizing the number of cashiers they need to hire.

Internally, Node keeps an event loop of functions to be completed in sequence. Hence, the code written by you never has to deal with the complexities of multi-threading.  In addition to this, however, Node has something called "non-blocking IO", where calls to IO are run on another thread, and when the work is completed the callback function is put in the event loop.  In this way Node can be servicing many IO operations at once while still remaining responsive to events not requiring any IO.  This makes a dramatic improvement to the performance because typical IO calls are very slow when compared to in-memory operations.

Note that this callback mechanism will 'loose' the stack trace containing what function called for the initial IO request.  This can be problematic when debugging and work is being done to address this soon. However, this also keeps the stack from getting very deep.  Shorter stacks are very beneficial because recursive algorithms can be taken advantage of in places where they would traditionally produce a stack overflow.  However, caution must be used when doing this because some callbacks, especially those not making IO requests, will not make use of the event loop and therefore will add to the stack growth.  

Install node.js and npm 

Node was developed on the Linux platform, and functions best there, but it also works on Windows and OS X. The examples here were run on Ubuntu 11.10 but they should work without much effort on the other platforms. Installers for Windows and OS X can be downloaded from the main site

Unfortunately, the Ubuntu repository does not keep up with the latest releases due to rapid growth surrounding Node.  You can download the Node source from However, to simplify the install process for the latest stable version on Ubuntu just run the following:

sudo apt-get install python-software-properties
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs
sudo apt-get install npm 

Notice that the last step installed the Node package manager.  Node is capable of supporting many kinds of network applications, but it is just a platform.  Most of the heavy lifting is done by a rich set of community supported modules.  Because of the large number of developers familiar with JavaScript the list of useful modules has grown very quickly.  To help in finding that perfect module to simplify your task and brighten your day they have put together a cool NPM search tool.

The examples below will use the following modules.  Take some time to visit their sites.  These modules have a lot to offer that we do not have time to demonstrate here.

Use npm to install the modules we need for our simple examples.

npm install mongodb --mongodb:native
npm install
npm install async
npm install optimist
npm install node-static

The extra argument for installing the mongodb driver demonstrates that modules are not restricted to JavaScript only. In this case the mongodb driver has its own parser in C++ which can be compiled to the native platform for better performance.  We will not be using this in the example because the JavaScript implementation turns out to be very performant.   In general, modules should stick to JavaScript for simplicity and cross-platform support unless there is a compelling reason to jump out into native code.

Start up a test database

Download the appropriate production release of MongoDB for your platform and extract it into your home folder ~

At the ~$ terminal enter the following to start up the database.

cd mongo*
mkdir data
./bin/mongod --dbpath ./data

the database server is ready for use when you see

admin web console waiting for connections on port 28017

If you need to stop the server press ctrl-c. Once the server has stopped, delete all the files in the ./data folder to start again fresh.

Execute the writing documents example

Review the writeExample.js file below. Its usage is very simple.

node writeExample.js [--async] [--forever]

Each call to the writeExample.js script will write 100000 random documents to the database.  If the --forever argument is passed, it will repeat until ctrl-c is pressed.  This is used as a source of ongoing events for the rest of the example.  MongoDB supports capped collections which have a fixed size and write over the oldest documents when full.  These are commonly used for logs. However, it will also work well for the simple example here.

Without the --async argument the example will synchronously write to the database by waiting for each write to complete before starting the next.  With the --async argument it fires off all the document writes without waiting for any response.

Reviewing the write document example

Applications written in Node may be difficult to follow at first, but with more experience they become straightforward.  In traditional applications the sequential nature of the program flows from the top down.  This is still true in Node. However, the convention is to make use of callbacks to continue processing after requesting any IO operations.

Node makes use of require('') to load needed modules into scope.  For example, the optimist module greatly simplifies command line arguments parsing by converting the arguments directly into properties.  Notice how the argv object is used on line 54 after the arguments are converted on line 15.

This example must write a fixed number of documents into a test database but it does not make use of for, each, while or any other traditional loop constructs.  Instead callbacks are used and situations that require sequential processing are easily implemented by the helper methods from the async module.  The async module makes use of the event queue within the Node framework to break work up and prevent event queue blocking.

MongoDB can support both synchronous and asynchronous writes.  The write example makes use of both of these in the insertOne() function.  In the async side of the conditional, the write is sent to the database, but insertOne() is not directly called again.  Instead, it's passed into the process.nextTick() function to be called upon during the next pass of the event queue.  If the code had made a traditional recursive call with the large number of documents to be inserted it would have resulted in a stack overflow.  The use of process.nextTick() allows all asynchronous calls in the event queue to be processed before the next call to insertOne() is processed.

The second half of the conditional could have implemented a simple call to insertOne() after collection.insert(). However, this example is a little more interesting.  In this part, async.parallel() is used to generate the next random document and update the progress bar while waiting on the IO to complete.  The async.parallel() calls its callback only when all the other functions have each called their callback.  In this way our example can take advantage of background processes without having to write a complex, multi-threaded implementation.

  1. 'use strict';
  3. var mongo = require('mongodb'), // driver from
  4. server = new mongo.Server('', 27017, {}),
  5. db = new mongo.Db('testDB', server, {native_parser: false}),
  6. TOTAL_DOCS = 100000, count = 0, progress = 0, startTime = new Date(), nextDoc,
  7. async = require('async'),
  8. progressTitle = " 0% _ _ _ _ _ _ _ _ _ _ _ _ 25% _ _ _ _ _ _ _ _ _ _ _ _ _ 50% _ _ _ _ _ _ _ _ _ _ _ _ _ 75%_ _ _ _ _ _ _ _ _ _ _ _ 100%",
  9. progressFactor = TOTAL_DOCS / progressTitle.length,
  11. data = {
  12. names: [ 'Bob', 'Chuck', 'Mike', 'Moe', 'Larry', 'Curly', 'Shemp', 'Rick', 'Don', 'Sam' ],
  13. foods: [ 'pizza', 'tacos', 'ice cream', 'steak', 'fried chicken' ]
  14. },
  15. argv = require('optimist').usage('Usage: node writeExample.js [--async] [--forever]').argv;
  17. // randomly returns true or false
  18. var randomBoolean = function () {
  19. return Math.random() > 0.5;
  20. };
  22. var updateProgress = function () {
  23. while (progress < (count / progressFactor)) {
  24. process.stdout.write('=');
  25. progress = progress + 1;
  26. }
  27. };
  29. var randomDocument = function () {
  30. // random birthday, food list, course score and parking location
  31. var rnd1 = Math.random(), rnd2 = Math.random(), rnd3 = Math.random(),
  32. personName = data.names[count % data.names.length] + '_' + count,
  33. bDate = new Date(1900 + (rnd1 * 100), rnd2 * 12, rnd3 * 28),
  34. favFoods = data.foods.filter(randomBoolean), artCourse = {
  35. subject: "art",
  36. finalscore: rnd3 * MAX_SCORE
  37. }, parkingSpot = {
  38. row: Math.round(rnd1 * MAX_PARKING_ROWS),
  39. aisle: Math.round(rnd2 * MAX_PARKING_AISLES),
  40. floor: Math.round(rnd3 * MAX_PARKING_FLOORS)
  41. };
  42. return {
  43. firstname: personName,
  44. course: artCourse,
  45. parking: parkingSpot,
  46. birthday: bDate,
  47. food: favFoods
  48. };
  49. };
  51. var wrapUp;
  52. var insertOne = function (collection) {
  54. if (argv.async) {
  55. //look ma no loop!
  56. count = count + 1;
  57. updateProgress();
  58. collection.insert(randomDocument());//fire, forget and hope
  59. //direct recursion in node is not recommended due to stack size limitations
  60. //and it would prevent other events from getting processed
  61. //nextTick however puts this function on the end of the even queue to be called
  62. //after the next pass.
  63. process.nextTick(function () {
  64. if (count < TOTAL_DOCS) {
  65. insertOne(collection);
  66. } else {
  67. wrapUp(collection);
  68. }
  69. });
  71. } else {
  72. //callback event from the insert triggers the next
  74. async.parallel([ function (callback) {
  75. collection.insert(nextDoc,
  76. //the call back will not be called until new doc is saved to disk
  77. {
  78. safe: true
  79. }, callback);
  80. },
  81. //because we are waiting on the write we can get this work done early
  82. function (callback) {
  83. count = count + 1;
  84. updateProgress();
  85. nextDoc = randomDocument();
  86. callback();
  87. } ],
  88. //only called when all the functions in the above array have called their callback
  89. function () {
  90. if (count < TOTAL_DOCS) {
  91. insertOne(collection);
  92. } else {
  93. wrapUp(collection);
  94. }
  95. });
  96. }
  97. };
  99. var writeData = function (collection) {
  100. count = 0;
  101. progress = 0;
  102. startTime = new Date();
  103. collection.count(function (err, originalCount) {
  104. console.log("");
  105. console.log("total docs before insert:" + originalCount);
  106. console.log((argv.async ? "now starting %d async writes"
  107. : "now starting %d synchronous writes"), TOTAL_DOCS);
  108. console.log(progressTitle);
  109. insertOne(collection);
  110. });
  111. };
  113. wrapUp = function (collection) {
  114. process.stdout.write('\n');
  115. collection.count(function (err, finalCount) {
  116. console.log("total docs after insert:" + finalCount);
  118. var sentDocsPerMs = count / (new Date().getTime() - startTime.getTime());
  119. console.log("sent %d documents at %d docs/ms to the server",
  120. TOTAL_DOCS, sentDocsPerMs);
  122. if (argv.forever) {
  123. //this will be repeated forever but we do not need to worry about stack overflow
  124. //wrapup() is always used as in a callback where it is known that the previous stack is lost
  125. writeData(collection);
  126. } else {
  127. //shutdown
  128. db.close();
  129. }
  130. });
  131. };
  133. // calls function when database is ready
  134. (err) {
  135. if (err) {
  136. console.warn(err.messsage);
  137. process.exit(1);
  138. }
  139. //will not create new collections when referenced
  140. db.strict = true;
  142. db.collection('testCollection', function (err, collection) {
  143. nextDoc = randomDocument();
  144. if (err) {
  145. console.warn("collection not found, building...");
  146. //only create if it was not already found
  147. db.strict = false;
  149. db.createCollection('testCollection', {
  150. 'capped': true,
  151. 'size': 1073741824 //don't need more than 1G for this
  152. },
  153. function (err, collection) {
  154. if (err) {
  155. console.warn("unable to create collection:" + err.message);
  156. return;
  157. }
  158. console.warn("created new capped collection");
  159. collection.createIndex([
  160. [ '_id' ],
  161. [ '_id', 1 ]
  162. ],
  163. function () {
  164. writeData(collection);
  165. });
  167. });
  168. } else {
  169. db.strict = false;
  170. writeData(collection);
  171. }
  172. });
  173. });//open

Execute the tail example

Review the tailExample.js file below. Its usage is also simple.

node tailExample.js [--server]

This small script makes use of MongoDBs tailing feature to 'stream' all the newly written documents to a client indefinitely.  Without the --server argument the script will simply write all the received documents to the console.  With the --server argument  it will open a web server on the local host so a browser can hit and watch data flicker by as the documents per second are tracked.  Note that in order for the server version to work there must be a folder named www in the same folder with the tailExample.js file.  The www folder must contain the example index.html file.

Reviewing the trailing example

MongoDB supports a feature on capped collections called a tailing cursor.  When using a traditional cursor the caller will receive a fixed set of results corresponding to the query.  When using a tailing cursor it will continue to return new documents that pass the criteria even if they were not in the collection when the cursor was first opened.  In this way we can use MongoDB to "push" document events into our example.

The sendData() method is connecting to the database and finding the last document and then building a tailing cursor for all newer documents.  The query restricts the results to the firstname and birthday fields just to demonstrate how it can be done.  The code looks very similar to the write example in that the execution flow follows the callbacks.  It is a good practice in Node to use the callback convention whenever apropriate as was done by the sendData() function signature.  Once the cursor is primed and ready to go it is sent back to the caller.  This helps separate concerns in such a way that the database work will not be tightly integrated with the consumer of these documents.

Lines 74-85 start up the server instance.  Ignoring line 82 that requires the rest of this block starts up a simple HTML server that will serve any files put into the www folder.  This is all done by the node-static module which additionally has an in-memory cache for these files so it is very performant.  The module on line 82 is worth pointing out because it is listening to all the requests coming into the server and can respond as well.  This is not for sending our data but rather it is for sending the client-side module down to the HTML page.  The index.html file contains only this element for fetching the the required client-side script.

<script src="http://localhost:8081/"></script>

No other files besides index.html were put into the www example folder,  this is often confusing for new users of the module.  The server-side module watches for the request and replies with the the right script file.  Once both sides have the right code, will let us open a connection suitable for pushing documents to the client. supports web sockets but it also supports graceful fallback to older communication technologies based on what the browser can support.  All this complexity is hidden so the only thing the server needs to do is define event handlers for 'connection', 'disconnect', and to emit messages on lines 87, 92 and 105.

The example server can easily support many concurrent browser connections.  Each time a new 'connection' event is received, the socket for that new browser is added to the array of clients.  When documents are received we could have looped over this array and emited documents to each socket, but that would have added an unnecessary blocking loop and caused the transmissions to be done in series.  On line 104 the async module is used once again to improve the performance by making better use of Nodes event loop.  The forEach function will call the emit function for all of the clients in parallel.  Once all the functions have called their respective callbacks, it will call its own callback which will use nextTick() to schedule the next call to nextObject().

At first glance it might appear that using nextTick() is not necessary. However, after testing, it appears that if there is only one function to be called by the forEach() method it calls back on the same stack context.  If that is allowed to happen it will likely cause a stack overflow.  This is not a unique situation. As I stated before; it is something you must watch for when developing for Node.  Something similar happens in the MongoDB driver when using unsafe writes.  The driver in that case immediately calls back and does so in the same stack context.  The nextTick()function is an excellent way to guard against this.

  1. 'use strict';
  3. var mongo = require('mongodb'),
  4. server = new mongo.Server('', 27017, {}),
  5. db = new mongo.Db('testDB', server),
  6. async = require('async'),
  7. argv = require('optimist').usage('Usage: node tailExample.js [--server]').argv;
  9. var sendData = function (consumerCallback) {
  10. // calls function when database is ready
  11. (err) {
  12. if (err) {
  13. console.warn(err.messsage);
  14. process.exit(1);
  15. }
  16. process.on('SIGINT', function () {
  17. db.close();
  18."stopped cursor because of interrupt");
  19. process.exit(0);
  20. });
  21. // calls function when the collection is ready
  22. db.collection('testCollection', function (err, collection) {
  23. console.log("starting tail...");
  24. if (err) {
  25. console.warn(err.messsage);
  26. process.exit(1);
  27. }
  28. // look for last document on startup
  29. collection.findOne({}, {
  30. 'limit': 1,
  31. 'sort': {
  32. '$natural': -1
  33. }
  34. }, function (err, doc) {
  35. // now find all the new documents after the last one found
  36. var query = (!doc ? {} : {
  37. '_id': {
  38. '$gte': doc._id
  39. }}),
  40. cursor = collection.find(query, {
  41. 'firstname': 1,
  42. 'birthday': 1,
  43. '_id': 1
  44. },
  45. {
  46. 'tailable': 1,
  47. 'sort': {
  48. '$natural': 1
  49. }
  50. });
  51. // call for the first object before any connections are made
  52. // because the MongoDB cursor is lazily initalized
  53. cursor.nextObject(function (err, item) {
  54. if (err) {
  55. console.warn("Collection:" + err.message);
  56. process.exit(1);
  57. }
  59. console.log("server is ready");
  60. // note that we are not looping here because we want
  61. // to provide the opportunity to take advantage of nodes
  62. // event loop
  63. consumerCallback(cursor);
  64. });
  65. });
  66. });// db.collection
  67. });//
  68. };
  70. var nextObject;
  72. if (argv.server) {
  74. var clients = [],
  75. ns = require('node-static'),
  76. http = require('http'),
  77. files = new ns.Server('./www'),
  78. app = http.createServer(function (request, response) {
  79. request.addListener('end', function () {
  80. files.serve(request, response);
  81. });
  82. }),
  83. io = require('').listen(app); // returns client side
  84. // upon request
  86. app.listen(8081);
  88. io.sockets.on('connection', function (socket) {
  89. console.log("connected");
  90. clients.push(socket);
  91. });
  93. io.sockets.on('disconnect', function (socket) {
  94. console.log("disconnected");
  95. clients.pull(clients.indexOf(socket));
  96. });
  98. nextObject = function (cursor) {
  99. cursor.nextObject(function (err, item) {
  100. if (err) {
  101. console.warn(err);
  102. process.exit(1);
  103. }
  104. if (item) {
  105. async.forEach(clients, function (socket, callback) {
  106. socket.emit('JSON', item);
  107. callback();
  108. }, function () {
  109. process.nextTick(function () {
  110. nextObject(cursor);
  111. });
  112. });
  113. }
  114. });
  115. };
  116. io.set('log level', 1); // very verbose without this
  117. console.log('Server running at');
  118. } else {
  119. nextObject = function (cursor) {
  120. cursor.each(function (err, item) {
  121. if (err || !item) {
  122. console.warn(err);
  123. process.exit(1);
  124. }
  125. console.log(JSON.stringify(item));
  126. });
  127. };
  128. }
  129. sendData(nextObject);

This index.html file should be put into the .www folder which is relative to the tailExample.js file.

  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4. <title> example</title>
  5. <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  6. </head>
  7. <body>
  8. <div id="state"></div>
  9. <ul>
  10. <li>Id: <input id="_id" size="24"/></li>
  11. <li>Name: <input id="firstname" size="12"/></li>
  12. <li>Birthday: <input id="birthday" size="24"/></li>
  13. <li>Documents per ms: <input id="dpms" size="6"/></li>
  14. </ul>
  16. <script src="http://localhost:8081/"></script>
  17. <script src=""></script>
  18. <script type="text/javascript">
  19. var webSocket = io.connect('http://localhost:8081');
  21. webSocket.on('connect', function() {
  22. $('#state').replaceWith('<b>Connected to server.</b>');
  23. });
  25. var startTime;
  26. var count = 0;
  28. webSocket.on('JSON', function(obj) {
  30. count ++;
  31. $('#_id').val(obj._id);
  32. $('#firstname').val(obj.firstname);
  33. $('#birthday').val(obj.birthday);
  35. if (count%200==0) {
  36. if (!startTime) {
  37. startTime = new Date();
  38. count = 0;//we just started the timer now
  39. } else {
  40. //update the rate
  41. var receivedDocsPerMs = count/(new Date().getTime()-startTime.getTime());
  42. $('#dpms').val(receivedDocsPerMs);
  43. }
  44. }
  45. });
  47. webSocket.on('disconnect', function() {
  48. $('#state').replaceWith('<b>Disconnected from server.</b>');
  49. });
  50. </script>
  51. </body>
  52. </html>


Node has demonstrated surprising performance, ease of use, a devoted fan base, and good technical design.  All of these are good reasons for its ongoing future success and growth. However, Node may also be one of those innovations that happened at just the right time.  Many companies are running into the limits of their non-event-driven implementations and are looking for ways to support ever greater numbers of users with their existing hardware.  They are asking, "How can I do more with less?" The answer might just be node.js.


Home of node.js

NPM search utility

Home of MongoDB

SETT on MongoDB Performance, Durability and Consistency

Example files