Our great sponsors
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.
goose
We haven't tracked posts mentioning goose yet.
Tracking mentions began in Dec 2020.
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
-
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.
- Give examples of really cool software made by a single developer?
-
Saving a Third of Our Memory by Re-ordering Go Struct Fields - Qvault
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.
-
Best way to store logs?
I think you should do some testing. Iteration and range query is right in the readme of boltdb, https://github.com/boltdb/bolt.
What are some alternatives?
migrate - Database migrations. CLI and Golang library.
sql-migrate - SQL schema migration tool for Go.
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
badger - Fast key-value DB in Go.
bbolt - An embedded key/value database for Go.
goleveldb - LevelDB key/value database in Go.
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
go-memdb - Golang in-memory database built on immutable radix trees
rqlite - The lightweight, distributed relational database built on SQLite.
go-cache - An in-memory key:value store/cache (similar to Memcached) library for Go, suitable for single-machine applications.
tiedot - A rudimentary implementation of a basic document (NoSQL) database in Go
ledisdb - A high performance NoSQL Database Server powered by Go