| badger | bolt | |
|---|---|---|
| 30 | 22 | |
| 14,043 | 11,201 | |
| 0.9% | - | |
| 8.4 | 0.0 | |
| 7 days ago | almost 7 years ago | |
| Go | Go | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
badger
-
Anytype helper crashed
github.com/dgraph-io/badger/v3/table.OpenTable(0xc000bb4000, {0x0, 0x1, 0x200000, 0x0, 0x0, 0x3f847ae147ae147b, 0x1000, 0x0, 0x0, ...})
- What would be some database with extreme raw performance? (details in)
-
GORM
I' see that I'm also set to check out BadgerDB next. https://github.com/dgraph-io/badger
-
Polygon: Json Database System designed to run on small servers (as low as 16MB) and still be fast and flexible.
Some example of embeddable database could be genji, badger and boltdb
-
Butter from two CoWs: making a key-value store with btrfs
As I mentioned in a comment above you could probably just use AgageDb (Rust implementation of Badger which is a single file high performance KVP store. Turn off all of its built-in transactional behaviour and see how fast it runs on BTRFS using reflinks instead.
-
Building a Log-Structured Merge Tree in Go
Badger: Fast key-value DB in Go (GitHub)
-
Is there a nice embedded json db, like PoloDB (Rust) for Golang
I use Badger a lot, it doesn’t do much but it’s fast
- Best packages?
- What's the big deal about key-value databases like FoundationDB ands RocksDB?
-
badger VS ZoneTree - a user suggested alternative
2 projects | 22 Aug 2022
bolt
-
Announcing jammdb: a simple single-file key/value store
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!
-
Polygon: Json Database System designed to run on small servers (as low as 16MB) and still be fast and flexible.
Some example of embeddable database could be genji, badger and boltdb
- Resource for making database from scratch
-
Ask HN: Books on designing disk-optimized data structures?
Designing Data Intensive applications- specifically chapter 3 and 4 which deal with strategies and algorithms for storing and encoding data to be stored on disk and their pros and cons.
Once you read that, I'll suggest reading the source of a simple embedded key-value database, I wouldn't bother with RDBMs as they are complex beasts and contain way more than you need. BoltDB is a good project to read the source of https://github.com/boltdb/bolt, the whole thing is <10k lines of code and is a full blown production grade system with ACID semantics so packs a lot in those 10k and isn't just merely a toy.
-
GitHub examples of Go that's written really well?
Bolt db and Bolt db's author post to go with it.
-
Open Source Databases in Go
https://github.com/boltdb/bolt is a ACID B+ tree key-value store
- A Database for 2022
-
Single Dependency Stacks
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
- How can I batch events in second intervals?
- Give examples of really cool software made by a single developer?
What are some alternatives?
goleveldb - LevelDB key/value database in Go.
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
bbolt - An embedded key/value database for Go.
nutsdb - A simple, fast, embeddable, persistent key/value store written in pure Go. It supports fully serializable transactions and many data structures such as list, set, sorted set.
go-memdb - Golang in-memory database built on immutable radix trees
go-cache - An in-memory key:value store/cache (similar to Memcached) library for Go, suitable for single-machine applications.
rqlite - The lightweight, user-friendly, distributed relational database built on SQLite.
BigCache - Efficient cache for gigabytes of data written in Go.
InfluxDB - Scalable datastore for metrics, events, and real-time analytics