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.
bbolt
-
How to extract key-value versioning from BBoltDB in ETCD as a Go Code
Based on this [GitHub document](https://github.com/etcd-io/bbolt) for BBoltDB, we can understand that Go Code be used to create a BBoltDB database on the system. The key-values added & operations done on them in that Go Code are stored in the BBoltDB database.
-
Locker: Store secrets on your local file system.
A Locker is a store on your file system (built on top of the amazing bbolt).
-
Looking for fast, space-efficient key-lookup
- bbolt for storage on disk. In order to get the smallest db file size possible make sure you insert the keys in order and set:
- is it possible to create a social media with all apis without database saving all the data into a yml or a json?
-
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.
-
Open Source Databases in Go
bbolt - An embedded key/value database for Go.
-
Help to learn multithreading in Go
For learning goroutines and channels, I usually recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt. It's relatively simple and you're more likely to run into common manifestations of concurrency issues running disk operations.
-
[Noob] Question about Channels
If you would like to explore usage of channels, I highly recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt.
-
A tiny NoSQL database
No transactions, no consistency guarantees, no benchmarks, global locks in the storage implementation, a collection is copied in its entirety on every insertion to it...I realize it's not for the same use case as MySQL or MongoDB, but a more obvious comparison here is e.g. https://github.com/etcd-io/bbolt. So why should someone use this over bbolt?
-
A pure Go embedded SQL database
use go-sqlite3 to work with sqlite3 is one choice.
https://github.com/etcd-io/bbolt is another pure go option.
cznic seems like an alternative to bbolt. nice to have some options.
sqlite
- Show HN: Roast my SQLite encryption at-rest
-
Show HN: My Go SQLite driver did poorly on a benchmark, so I fixed it
> I would've probably picked the modernc variation
Heads up about the modernc library, it has been stuck on an old version of sqlite for several months [1]. It seems like maintainer time is the limiting factor [2]. There has been a call to arms on that issue page, the maintainer is looking for help, but it looks like not much has arrived. It seems like it might trace back to blockers in the C-to-Go compiler.
It's a major undertaking and a very impressive piece of work, but I'm not surprised it's a struggle when big roadblocks get hit. I hope they find a way to progress, but I'm very relieved to be seeing some CGo-free alternatives like ncruces/go-sqlite3 emerging. I'm going to give it a try for sure and see if I can live with the compromises.
Squinn-go looks very compelling too, but I don't like that it requires the squinn binary to already be installed on a user's machine, I think that gives with one hand and takes with the other: sure, I get to avoid CGo, but I also lose the turnkey, single-command install, static build benefits Go brings out of the box.
Seconding the point about nitty gritty, I'd read it for sure too!
[1]: https://gitlab.com/cznic/sqlite/-/issues/154
-
Show HN: Sqinn-Go is a Golang library for accessing SQLite databases in pure Go
No, but that has the disadvantage of being C compiled into Go, then being compiled into native executable.
I'm actually surprised by how readable this came out; props to the Go->C compiler author. But you can guess that pushing this sort of thing through the Go compiler is going to cause some slowdowns due to sheer paradigm mismatch: https://gitlab.com/cznic/sqlite/-/blob/master/lib/sqlite_lin...
-
Show HN: MongoDB Protocol for SQLite
FWIW, we use a version of SQLite transpiled into Go to avoid CGI problems: https://gitlab.com/cznic/sqlite
-
Go port of SQLite without CGo
It could be clearer in the readme, but note that this is a machine translation from C to Go, repeated for every OS-Arch pair. Example of the one you're most likely to use in production: https://gitlab.com/cznic/sqlite/-/blob/master/lib/sqlite_linux_amd64.go
What are some alternatives?
badger - Fast key-value DB in Go.
chai - Modern embedded SQL database
bolt
ffi-overhead - comparing the c ffi (foreign function interface) overhead on various programming languages
goleveldb - LevelDB key/value database in Go.
sqlite - Go SQLite3 driver
go-sqlite - Low-level Go interface to SQLite 3
go-sqlite3 - sqlite3 driver for go using database/sql
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
sqlparser-rs - Extensible SQL Lexer and Parser for Rust
BigCache - Efficient cache for gigabytes of data written in Go.
proteus - A simple tool for generating an application's data access layer.