Node.js + CouchDB vs CouchDB

Question

I\'m questioning myself why should I use combination of Node.js + CouchDB versus CouchDB standalone approach. What are the benefits of getting Node.js into the game? Any comment

Answer 1

Nick's answer is a particularly intriguing one. To underline the approach, here's a video by Mikeal Rogers when he worked at CouchOne (?) suggesting the couchdb + node-behind approach: http://nosql.mypopescu.com/post/2896329122/node-js-couchdb-crazy-delicious.

On the other hand, I think there's one area that even that innovative approach falls down and that's (more sophisticated) security. Basic levels of security work fine, but if you want content controlled by more sophisticated levels of security, couchdb's map-reduce doesn't cut. However, some simple node.js could.

So for some security reasons (i.e., to avoid unsecured map-reduce results), node.js could be better on the front-end to implement those security measures.

FYI.