{{ !articles[0].partner.isSponsoringArticle ? "Platinum" : "Portal" }} Partner
java,news,high-perf,json,tools & methods,mongodb,node.js,dzone refcardz,socket.io,express,mongoose

Refcard Expansion Pack: Node.js

This week, DZone released an update of Refcard #141: Node.js. For those of you interested in learning more about Node.js or sharpening your skills - or, in some cases, debating a potentially unpopular opinion - we decided to dig into the DZone archives and find some of the most popular posts we've had on the topic over the past two years:

1. Performance Comparison Between Node.js and Java EE

  • Node.js has impressed me several times with high performance right out of the box. In my last Node.js project it was the same: we beat the given performance targets without having to tweak the application at all. I wanted to know: how would Java EE compare to Node.js in this particular case?

2. Getting Started with Socket.IO and Node.js

  • Node.js is not the cure for everything, however, it can certainly makes working with Websockets very easy when using the Socket.io library. Using websockets you can easily build realtime applications and even multi-player games. Today I’ll show you how to easily build a simple chat program using Node.js and Socket.io.

3. A simple Node.js web application that uses Mongoose, Express and MongoDB and returns JSON

  • Today I’m going to show you how to build a simple application that uses Nodejs, Mongoose, Express and MongoDB that will persist some data and get it back. It will also have a simple configuration file so I can configure my routes in Express.

4. What is Node.js and why should I care?

  • As an operations guy I really don’t keep up with the latest and greatest when it comes to software development. I often hear developers discussing new languages or libraries but rarely care enough to jump in and figure out why it’s important to me. I’ve heard a lot of discussion about Node.js and seen many tweets, blogs, and articles that reference the term but up until now I haven’t really had the need or desire to jump in and figure out why it’s important.

5. 40+ Resources for the Node.js Developer

  • From node.js on Openshift to node.js patterns and 3rd party modules, here's an extensive list of node.js resources for your perusal.

And don't forget to download the Node.js Refcard itself:


By Bert Belder

In-browser JavaScript? Sure. But on the server? Wow! But how? What about...stuff servers do? Like read from spinning plates? Http with a thousand clients at once? What an I/O nightmare! In a single thread? No way!

Node.js says "no problem." Just write JavaScript. Asynchronicity is free. The Node.js wizardry (=event loops + callbacks) handles the rest. And here's some more magic: We've worked with one of the Node core committers to update our Node.js Refcard to cover the latest version (v0.12) before it's even released. Sweet.

This Refcard covers:

  • Node architecture
  • Node Package Manager
  • What's new in v0.12
  • Node API guide... and more!


{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks