Node.js the Right Way: Practical Server-Side JavaScript That Scales

By Jim R. Wilson
ISBN-13: 978-1937785734

Node.js the Right Way is a fantastic little book. It’s a small book (but then it’s Pragmatic exPress) and it doesn’t go into anything in much detail, but then that’s what makes it fantastic. It gives a useful and practical overview of writing Node.js server side applications and explains many of the tools and JavaScript patterns which will be useful to Node.js programmers.

It starts off with examples of manipulating the local file system using Node.js. This struck me a little odd as the only thing I tend to use the local file system for is reading configuration files. If I need to write a file I tend to put it in Amazon S3. However, this is genius and looking at how to manipulate the filesystem gives some useful insights into Node.js programming.

The book then goes on to look at networking with sockets, something which is often neglected in a world where we expect everything to be RESTful. There’s then a tour through scalable messaging, including clustering, how to access databases and how to write web services, including JavaScript promises and generators!

The final chapter covers writing a web application with a single page front end and authentication. This is the only place the book falls down. Too much is covered in two short a chapter. It’s still quite useful though.

This is not a book for a novice JavaScript or even a novice Node.js developer, but for once a little knowledge is not a dangerous thing and Node.js the Right Way will help increase that knowledge. It even led me to believe JavaScript might actually be the future.

Comments

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Paul Grenyer

Search This Blog