Storm
Simple and powerful toolkit for BoltDB (by asdine)
gosqlparser
Simple SQL parser (by krasun)
Our great sponsors
| Storm | gosqlparser | |
|---|---|---|
| 4 | 3 | |
| 2,040 | 58 | |
| - | - | |
| 0.0 | 0.0 | |
| 3 months ago | over 2 years ago | |
| Go | Go | |
| MIT License | MIT License |
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.
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
gosqlparser
Posts with mentions or reviews of gosqlparser.
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.
-
A simple SQL parser in Go
As part of my toy database development, I wrote a simple SQL parser as a dedicated library. I decided to share it with the community to get feedback and be useful 👉 github.com/krasun/gosqlparser.
-
Anyone interested in getting their story with Go up for my newsletter?
Hey 👋 I recently finished writing a SQL parser for my toy database (in Go). I absolutely love the language and the simplicity it markets. I can share my story with Go. Let me know if you are interested.
What are some alternatives?
When comparing Storm and gosqlparser you can also consider the following projects:
GORM - The fantastic ORM library for Golang, aims to be developer friendly
kyoto - Golang SSR-first Frontend Library
beego orm
gotimeparser - Golang time parser. This library provides an ability to parse time from many different formats at the same time.
go-pg - Golang ORM with focus on PostgreSQL features and performance
sqlc - Generate type-safe code from SQL
upper.io/db - Data access layer for PostgreSQL, CockroachDB, MySQL, SQLite and MongoDB with ORM-like features.
goselect - SQL like 'select' interface for files
gomodel
participle - A parser library for Go
Zoom - A blazing-fast datastore and querying engine for Go built on Redis.
fbptree - A persistent storage (in file) based using B+ tree with byte-slice keys and values