bbolt VS pebble

Based on this [GitHub document](https://github.com/etcd-io/bbolt) for BBoltDB, we can understand that Go Code be used to create a BBoltDB database on the system. The key-values added & operations done on them in that Go Code are stored in the BBoltDB database.

A Locker is a store on your file system (built on top of the amazing bbolt).

- bbolt for storage on disk. In order to get the smallest db file size possible make sure you insert the keys in order and set:

I'm wanting to store some wasm modules (as []byte) in BoltDB. Right now the modules are <1MB, but eventually, they could be 10-50MB in size. Is this going to reduce the performance of BoltDB all around, if the size of a value is this large? If it makes a difference, I'm using the Storm toolkit for querying.

bbolt - An embedded key/value database for Go.

For learning goroutines and channels, I usually recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt. It's relatively simple and you're more likely to run into common manifestations of concurrency issues running disk operations.

If you would like to explore usage of channels, I highly recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt.

No transactions, no consistency guarantees, no benchmarks, global locks in the storage implementation, a collection is copied in its entirety on every insertion to it...I realize it's not for the same use case as MySQL or MongoDB, but a more obvious comparison here is e.g. https://github.com/etcd-io/bbolt. So why should someone use this over bbolt?

use go-sqlite3 to work with sqlite3 is one choice.

https://github.com/etcd-io/bbolt is another pure go option.

cznic seems like an alternative to bbolt. nice to have some options.

To improve the compacting speed of L0 files, we took inspiration from the design of the CockroachDB storage engine pebble.

https://github.com/cockroachdb/pebble ?

Pebble is a LevelDB/RocksDB-inspired key-value database focused on performance. PebbleDB is replacing Fantom’s previous RPC software to match Fantom’s sheer throughput. PebbleDB is consistently faster than previous options and it has helped the Fantom network to consistently reach synchronization with the network quicker while reducing the duration of API requests.

https://github.com/cockroachdb/pebble Pure go SSD native key-value store. You could think of it as map[[]byte][]byte on persistent storage.

Genji is a document-oriented, embedded, SQL database. It is build over Pebble which is a port of RocksDB in Go, by the authors of CockroachDB.

Out of curiosity, why write https://github.com/cockroachdb/pebble and not just use https://github.com/dgraph-io/badger?

There's the semi-recent pebble from the folks that make cockroach db. Haven't used it, but seems promising: https://github.com/cockroachdb/pebble