node.js database [closed]

Answer 1

dirty is yet another flat-file key-value store. As the name suggests, it's a quick and dirty but performant solution for simple cases. I'm not the author :)

Answer 2

Although your choice very much depends on the features you are going for, I really appreciate CouchDB for its native JavaScript environment. Both data and views are written in JavaScript so it fits very well to node.js in my opinion.

There are also different client libraries available, some are rather low level, other really very abstracted.

But as I said, you should also think about the features that you require for your database.

Answer 3

I'm not sure the correct solution is to solely focus on mapping a database to your web stack, but rather also considering application-specific requirements.

Are you analyzing twitter feeds or other high-volume data for patterns, but don't need transactional support? Then pick something really fast.

Do you just want to store some really basic info in a few tables and its currently not an "enterprise focused" app? Then pick something cool to learn.

Maybe you are going to store data thats really important to a client, robust, needs to be transactional, and have live replication to remote hosting facilities, etc. Then maybe look at something like postgresql. It wouldn't mirror as well, but the node.js driver works pretty well and if you aren't deathly afraid of sql it gets what you want in/out pretty easily.

As for my own opinion, I think going with a newer stack like node.js (vs traditional frameworks in php/java) is adding enough "new" complexity that one shouldn't add extra layers all at once. This is a good article that discusses that:

http://nodeguide.com/convincing_the_boss.html

Answer 4

Some more to consider:

Globals: http://globalsdb.org

GT.M (see https://github.com/robtweed/node-mwire for a starting point)

M/DB (an open source clone of SimpleDB): https://github.com/robtweed/node-mdb and you can use the Node.js SimpleDB client to access it: https://github.com/rjrodger/simpledb

Answer 5

I'll speak from my experience: CouchDB comes with a definite learning curve, whereas MongoDB I found to be very easy to learn and set up. I have never used redis. I suggest MongoDB - but that maybe shameless fanboyism - I have no numbers, heh, only claims of ease of use.