Site: http://apiplayground.org
Source: http://github.com/jashkenas/api-playground/blob/master/src/a...
The source is interesting because it demonstrates something that you can't do easily with a regular Rails/Django app: nonblocking asynchronous calls to remote APIs, with synchronous responses to the ajax request.
It was discussed a while back on HN: http://news.ycombinator.com/item?id=1477084
This source is on GitHub here: http://github.com/mape/node-wargames
Also, Node Knockout (http://nodeknockout.com/, a 'build a node app in 48 hours' competition) is happening at the end of August, and I expect some cool stuff to come out of that.
The developers wrote about using node on their blog: http://debuggable.com/posts/parsing-file-uploads-at-500-mb-s...
http://rfw.posterous.com/how-nodejs-saved-my-web-application
I know it is a rather interesting tech but other than that what do you/would you use Node.js for?
- You get to write JavaScript on your back-end and your front-end.
- It's evented (like Twisted, EventMachine, etc) which has proven popular/robust/fast recently (think FriendFeed).
- It handles insane amounts of requests/second (due to non-blocking IO and V8 awesomeness among other things).
- Did I mention you get to write more JavaScript? :)
- It makes it pretty easy to implement servers for other protocols than just straight vanilla http -- for example WebSockets implementations and so on.
Node is great for handling many concurrent clients. It extends the V8 interpreter with excellent low-level APIs: Posix, Tcp, Http, DNS. If you need to share Javascript code between client and server, Node is the best server-side Javascript environment you could choose to use.
http://demo.hummingbirdstats.com/
http://rdelsalle.blogspot.com/2010/05/real-time-web-analytic...
node.js + google maps + faye comet library