bolt VS goleveldb

This crate started out as just a way for me to learn how boltdb works, while learning Rust at the same time. But somehow people started finding and using it and seem to like the simple API, so I figured I might as well share it in case someone else finds it useful too. If you want to know more about my motivations and the history of this crate, you can read the release notes on version 0.8.0!

Some example of embeddable database could be genji, badger and boltdb

Bolt db and Bolt db's author post to go with it.

https://github.com/boltdb/bolt is a ACID B+ tree key-value store

For a single server, SQLite, or boltdb[0]

I've never had to scale horizontally. I develop in Go and you can get very far along with just vertical scaling (aka beefier hardware).

Therefore I can't give concrete examples of a distributed db-as-a-library.

But all that you need is to extend the functions that fetch data to not just fetch from disk but from "peers" as well. For this to work you need servers (instances) to know about each other, and as you add more they also get added to their peers - sort of like a bittorrent network. I don't think it's difficult to do.

SQLite might not be suited for being distributed (although RQlite[1] claims to have done it).

Making a distributed data storage based on boltdb[0] is probably more feasible.

Whatever the case, there's no reason why a data storage engine can't be a library, even if it's distributed.

[0]: https://github.com/boltdb/bolt

[1]: https://github.com/rqlite/rqlite

There's things like boltdb which maps a database file to memory and accesses it through raw structures with no serialization. Any changes to the structure layout would break it.

I think you should do some testing. Iteration and range query is right in the readme of boltdb, https://github.com/boltdb/bolt.

Looks like a job for GoLevelDB.

goleveldb - Implementation of the LevelDB key/value database in Go.

I wanted to get deeper insights into both indexeddb and leveldb, so decided to write an indexeddb wrapper around goleveldb.

https://github.com/syndtr/goleveldb for heavy-duty local data storage.

We're using go-leveldb for a reasonably high-load case here at my $dayjob.

I would used some embedded kv store like go-leveldb or bolt. Key is BigEnding timestamp + optional tail to allow duplicate timestamps.

I'm using the leveldb https://github.com/syndtr/goleveldb for the moment because I'm developing the architecture. Mh, leveldb support the only the inmem db? :/