Skip to main content

Book Review: Node Web Development

Node Web Development by David Herron is book written for those who want to start using Node.js for real Web Applications. Book is short and written for purpose of practical examples. Of course if it will be longer it would be even better but this is very good starting point for learning Node.js.
Book is rather short, and to be honest when I sow it I was thinking: This is too short! But just after first chapter I realize that maybe short, but chapters are full of examples and explanations. I was impressed how reading it changed my opinion.

Tips for other readers:
  • Use Node.js from 0.4 tree, mostly because of modules, most of them are not ported yet to 0.5.
  • If You want to create apps as fast as possible read chapter 5 at the end (except of those that want to use HTTPClient)
  • Install Databases before installing npm modules.
Links to book:

More about book:

I will write about chapters, for now You should already know that I like this book. What this book is about?

Good introduction, nothing more nothing less.

Besides what title: 
  • How to set up daemon
  • Forever - run node even if there are problems
  • Cluster - how to use all of You'r PC cores
I was impressed! These are awesome to know how to do them. Practical examples with descriptions how it works. 

Good chapter about modules, You can read it because it is sample chapter. Check link above.

From Hello World to Express Web Site, this chapter explains basic concepts but this is fun to refactor applications to Connect and Express.

This chapter is strange, for me part about "Simple Web Server" was pointless, and can be ignored. After that was Events and HTTPClient which are good to know. In my opinion this chapter should be about Express, not an attempt to write new Express. How often Web Developers write new web framework? Not so often. In my opinion this chapter can be ignored, read it as last.

Another good chapter, using Express and SQLite (do not use it for real websites) or MongoDB to run simple notes application. There was some points that I doesn't like (using ejs with <%= %> hell) but that was details, that do not break my opinion about chapter.  
There was short introduction to writing authentication, but it was only starting point. It would be better to include it, but 

I rate it 9/10, and why only 9?
Book is short, and chapter 5 disappoints me. I know that Node.js is changing very fast, and attempt to write longer one could be risky, but this book is so good that this is shame that it has only about 170pages!
Also chapter 5 could be more about Express, but I write this because others are so good that this one left me unsatisfied.

I changed rating while reviewing NetBeans IDE 7 Cookbook from 8 to 9. 


  1. Thanks you for this review!
    I'm going to buy this book today.
    Gogo node :)

  2. The book is sort of short if to consider but I think this short is very precise in giving details to the node.js matter.

    Web Development

  3. Thanks for comments.
    @Stacey this is how I think too!

  4. Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write ups thanks once again.
    Android app development| Android app developer| Android apps development|

  5. Yes I agree this is great one I expose the instruction impress to read the posting thanks By Regards SEO

  6. Thanks..Remember that the more time you spend on developing your website; the better and faster the results you will be able to get. If you have expertise in web development you can do it on your own. If you are not familiar with web designing, you can hire professionals to do it for you. Whichever approach you take; it is important to have a general idea of web development so that you can be clear about what you want and how you can achieve it in the best possible manner.
    tampa personal injury attorney

  7. This comment has been removed by the author.

  8. Hello there, I discovered your blog by means of Google whilst looking for a similar matter, your web site came up, it
    looks good. I've bookmarked it in my google bookmarks. Hello there, simply changed into aware of your blog via Google, and found that it's truly informative. I'm gonna be careful for brussels. I will be grateful in the event you continue this in future. Lots of folks shall be benefited from your writing.
    Flex developer London
    Flash developer London
    PHP developer London

  9. I don't even know how I ended up here, but I thought this post was great. I do not know who you are but definitely you are going to a famous blogger if you aren't already ;)
    Flex developer London


Post a Comment


Popular posts from this blog

How to simulate slow connection (developer proxy in Node.js)

Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy.

Toggle device modeChoose Network type.Refresh the page 


For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me.

I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one.

With this module I can write really short code to create slow server:

var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host: 'localhost', port: 8080, …

How to use NPM packages from private repositories on bitbucket

Using Node.js you want to use NPM packages for reusable parts of the apps you create, that is a common sense. At the same time not everything makes sense as a public module unfortunately. Right now we are using Bitbucket at work for private repositories but there is a problem. How to use them as NPM modules? We do not want to publish them to the public but still want to have an ability to install them easily.

After googling and experimenting I have found simple solution.
First create new user in your organization with obscure password and give it read access to the repo. It is best to assign really obscure password but do not fool yourself. This is convenient but you must sacrifice security a bit. You should always consider how in your context that would be important.

Change example from below to:
user - username
PASS - password of the user
organization - owner of the project (you can find it in bitbucket url to your project)
project - your project name