Tag Archives: node

JavaScript Development – A Year Later

Posted on by

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 our weekly shopping. It has had many shapes over the years; it started out as a plain Java Web application; then it changed to a REST based Scala backend with a plain JavaScript front end to go back to having a Java backend again. Now there is no Java, no Scala…just JavaScript.

The application just seemed to fall into place with Node. If you want a reasonably simple modern web application, Node is perfect. By “modern” I mean a very responsive web application typically with a JavaScript fat client. As it turns out, FeedMe now has a Node backend and a Backbone based JavaScript fat client. If anything, more work went into FeedMe this summer than last, even though there was no sabbatical this time. During the Crisp Hack Summit last weekend, Yassal and I dug deep and we’re getting close to having an actual application.

Although one man’s buzz is the next man’s old news, I think we won the buzzword bingo at the Summit. FeedMe uses the following technologies.

Yassal and I will be blogging about FeedMe and the technologies involved over the next couple of months.

The source (incomplete as it may be) can be found at: https://github.com/crispab/feedme

The Compelling Case for Node.js

Posted on by

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.

read more »

IntelliJ and nodeunit

Posted on by

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.

read more »