As some of you may remember, a year ago I took Q3 off to focus on building a JavaScript application. I learned a lot especially about Node.js. Yassal and I have a pet project called FeedMe that we have worked on over the years. FeedMe implements a shopping list for us to use when doing
Continue reading
The Compelling Case for Node.js
The basic premise of Node.js is that I/O is expensive and that, since I/O is expensive, we can’t block waiting for it to complete.
Many traditional Web Servers typically adopt a one thread per request approach, and any I/O (database, web service, file system call…) during the request blocks that thread of execution. This is inefficient in many ways because when the thread is blocked waiting for I/O to complete, it can’t respond to other requests.
IntelliJ and nodeunit
It turns out that I’ve gotten completely side tracked…or maybe not side tracked per se, but at least not completely focused on the client side of the Application. The past couple of weeks I’ve been engulfed in Node. Trying to figure out what it is, what I can do with it and obviously how I can test drive it. I found nodeunit which seemed to be a good testing framework candidate.