Vincent Weevers

> I need to know which part of the key parameter passed in to _put() is the sublevel prefix Why do you need this? For context.

Somewhat relevant: https://github.com/Level/abstract-level/issues/61

That stems from old `level-sublevel` conventions: https://github.com/hmalphettes/redisdown/pull/23. Since then, sublevels have become a builtin feature of `abstract-level`, and batch operations don't have a `prefix` option (we do have a `sublevel`...

Yeah, didn't get around to updating `awesome` yet. You could check https://www.npmjs.com/package/abstract-level?activeTab=dependents.

`rave-level` is shaping up, iterating (as a follower) at twice the speed of `level-party`, bringing it closer to `classic-level`: Click to expand 

Published [`many-level`](https://github.com/Level/many-level).

Depends on what functionality you need. Without iterators, simple `GET` and `SET` commands suffice and can easily be benchmarked against Level modules. For iterators, you need hashes and/or sorted sets,...

I got side tracked by a Node.js bug on Windows (https://github.com/nodejs/node/issues/42496) but that seems to be an edge case so I went ahead and published [`rave-level`](https://github.com/Level/rave-level).

Only question is, if `db` is a sublevel, should it forward `{ prewrite: false }` to its parent database? I think no, to keep it isolated.

The `prewrite` hook is fast, so technically this could also be solved in userland. Like so: ```js const bypass = Symbol('bypass') db.hooks.prewrite.add(function (op, batch) { if (op[bypass]) return }) await...