Haven't needed to use anything but key/value stores for the past four years, and have primarily used leveldb with great success. Ability to just npm install it removes a lot of hassle, plus it's very fast.
LevelDB is the right choice if you want to keep your persistence layer minimal. With smart choice of keys you can achieve a lot with very little. In fact, having no features can really help you to simplify your designs.
The ecosystem is good: https://github.com/Level/levelup/wiki/Modules
Particularly recommend looking into a sublevel tool like level-sublevel or level-spaces but it's also easy enough to just split your keys into namespaces yourself.
Big benefit is you can also use the same API and much of the ecosystem in the browser with tools like level-js: https://www.npmjs.com/package/level-js
[comment deleted]timoxley 3383 days ago. link 1 point ▲▼
This isn't unprecedented, all previous node's have released new versions shortly after stable version release, but also is expected given the high number & velocity of node's core maintainers at present.
Major release usually means orders of magnitude more people using the code, no matter how long and well-advertised your prerelease cycle is. More eyeballs means more chances to find bugs.
1. Be wary of tech that doesn't have code samples up front.
2. Be wary of tech that rubbishes the competition.
3. Be wary of tech that does 2) before getting to 1).
For more long-form coverage of these topics and more, I highly recommend Ilya Grigorik's book "High Performance Browser Networking", which is available to read online for free:
http://chimera.labs.oreilly.com/books/1230000000545/index.html
Of particularly high value are the chapters on TCP, UDP & HTTP2.