gosqldb
A key-value persistent database that supports SQL queries over B+ and LSM trees (by krasun)
Storm
Simple and powerful toolkit for BoltDB (by asdine)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
gosqldb
Posts with mentions or reviews of gosqldb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-11.
-
Resource for making database from scratch
For learning, I built components of the database engine like an SQL parser, a file-based B+ tree, a log-structured merge-tree. And I planned to merge them into the simple database engine. But I paused the project due to the changes in life obstacles.
Storm
Posts with mentions or reviews of Storm.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-11.
- Resource for making database from scratch
-
BoltDB performance hit with large values?
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.
-
Do you use an embedded NoSQL database?
I’ve used boltdb with storm, works well: https://github.com/asdine/storm
-
Using BoltDB as internal database 💾
Storm is a simple and powerful toolkit for BoltDB. Basically, Storm provides indexes, a wide range of methods to store and fetch data, an advanced query system, and much more. GitHub: https://github.com/asdine/storm
What are some alternatives?
When comparing gosqldb and Storm you can also consider the following projects:
fbptree - A persistent storage (in file) based using B+ tree with byte-slice keys and values
GORM - The fantastic ORM library for Golang, aims to be developer friendly
db_tutorial - Writing a sqlite clone from scratch in C
beego orm
chai - Modern embedded SQL database
go-pg - Golang ORM with focus on PostgreSQL features and performance
bolthold - BoltHold is an embeddable NoSQL store for Go types built on BoltDB
upper.io/db - Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.
bolt
gomodel
py-caskdb - (educational) build your own disk based KV store
Zoom - A blazing-fast datastore and querying engine for Go built on Redis.