News for hackers. Stuff that matters.
Re:NeDB, a pure Javascript database for Node.js and Node Webkit by louischatriot on Thursday June 20, 2013 @11:35AM (#5912682)
It's not supposed to work with cluster and using it with multiple programs that update/remove/insert docs will cause unexpected behaviour, although no data corruption since the datafile is append-only.

But if you need multiple programs to use your DB at once you need a more powerful solution such as MongoDB. The goal of NeDB is to bring DB features to desktop apps or low concurrency webapps, not replace Mongo and the like.

Re:NeDB, a pure Javascript database for Node.js and Node Webkit by baudehlo on Thursday June 20, 2013 @12:25PM (#5912980)
No I get that, I'm not saying it should support those things, just saying you should probably document it clearly. People don't like to lose data.

And append-only doesn't make you immune to corruption. There's still a possibility of two processes writing at the same time corrupting what gets written to the file.

Re:NeDB, a pure Javascript database for Node.js and Node Webkit by tlack on Thursday June 20, 2013 @01:26PM (#5913327)
Perhaps you should provide an option to have the db itself running as a child process (via cluster), and CRUD statements are actually proxied to that process (via a Unix pipe or socket) instead of updating the data directly in the process' state. This would work well as an extension.