Go Key-Value

Open-source Go projects categorized as Key-Value
Edit details
Topics: Database Go Golang Redis Distributed Systems
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured

Top 23 Go Key-Value Projects

  • etcd

    Distributed reliable key-value store for the most critical data of a distributed system

    • Project mention: Oracle Linux 8.8'de PostgreSQL 13 Yedekli Yapı Nasıl Kurulur? - Patroni, ETCD, HAProxy | dev.to | 2023-12-07

    sudo dnf -y install curl wget vim ETCD_RELEASE=$(curl -s https://api.github.com/repos/etcd-io/etcd/releases/latest|grep tag_name | cut -d '"' -f 4) echo $ETCD_RELEASE wget https://github.com/etcd-io/etcd/releases/download/${ETCD_RELEASE}/etcd-${ETCD_RELEASE}-linux-amd64.tar.gz tar xvf etcd-${ETCD_RELEASE}-linux-amd64.tar.gz cd etcd-${ETCD_RELEASE}-linux-amd64 sudo mv etcd* /usr/local/bin ls /usr/local/bin /usr/local/bin/etcd --version

  • badger

    Fast key-value DB in Go.

    • Project mention: Anytype helper crashed | /r/Anytype | 2023-12-09

    github.com/dgraph-io/badger/v3/table.OpenTable(0xc000bb4000, {0x0, 0x1, 0x200000, 0x0, 0x0, 0x3f847ae147ae147b, 0x1000, 0x0, 0x0, ...})

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo

  • immudb

    immudb - immutable database based on zero trust, SQL/Key-Value/Document model, tamperproof, data change history

    • Project mention: Ask HN: What is your experience of tamper proof systems? | news.ycombinator.com | 2024-01-05

  • buntdb

    BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support

    • Project mention: PostgreSQL: No More Vacuum, No More Bloat | news.ycombinator.com | 2023-07-15

    Experimental format to help readability of a long rant:

    1.

    According to the OP, there's a "terrifying tale of VACUUM in PostgreSQL," dating back to "a historical artifact that traces its roots back to the Berkeley Postgres project." (1986?)

    2.

    Maybe the whole idea of "use X, it has been battle-tested for [TIME], is robust, all the bugs have been and keep being fixed," etc., should not really be that attractive or realistic for at least a large subset of projects.

    3.

    In the case of Postgres, on top of piles of "historic code" and cruft, there's the fact that each user of Postgres installs and runs a huge software artifact with hundreds or even thousands of features and dependencies, of which every particular user may only use a tiny subset.

    4.

    In Kleppmann's DDOA [1], after explaining why the declarative SQL language is "better," he writes: "in databases, declarative query languages like SQL turned out to be much better than imperative query APIs." I find this footnote to the paragraph a bit ironic: "IMS and CODASYL both used imperative query APIs. Applications typically used COBOL code to iterate over records in the database, one record at a time." So, SQL was better than CODASYL and COBOL in a number of ways... big surprise?

    Postgres' own PL/pgSQL [2] is a language that (I imagine) most people would rather NOT use: hence a bunch of alternatives, including PL/v8, on its own a huge mass of additional complexity. SQL is definitely "COBOLESQUE" itself.

    5.

    Could we come up with something more minimal than SQL and looking less like COBOL? (Hopefully also getting rid of ORMs in the process). Also, I have found inspiring to see some people creating databases for themselves. Perhaps not a bad idea for small applications? For instance, I found BuntDB [3], which the developer seems to be using to run his own business [4]. Also, HYTRADBOI? :-) [5].

    6.

    A usual objection to use anything other than a stablished relational DB is "creating a database is too difficult for the average programmer." How about debugging PostgreSQL issues, developing new storage engines for it, or even building expertise on how to set up the instances properly and keep it alive and performant? Is that easier?

    I personally feel more capable of implementing a small, well-tested, problem-specific, small implementation of a B-Tree than learning how to develop Postgres extensions, become an expert in its configuration and internals, or debug its many issues.

    Another common opinion is "SQL is easy to use for non-programmers." But every person that knows SQL had to learn it somehow. I'm 100% confident that anyone able to learn SQL should be able to learn a simple, domain-specific, programming language designed for querying DBs. And how many of these people that are not able to program imperatively would be able to read a SQL EXPLAIN output and fix deficient queries? If they can, that supports even more the idea that they should be able to learn something different than SQL.

    ----

    1: https://dataintensive.net/

    2: https://www.postgresql.org/docs/7.3/plpgsql-examples.html

    3: https://github.com/tidwall/buntdb

    4: https://tile38.com/

    5: https://www.hytradboi.com/

  • rosedb

    Lightweight, fast and reliable key/value storage engine based on Bitcask.

    • Project mention: rosedb: A Lightweight Key/Value Storage Engine in Go | /r/golang | 2023-06-30

  • 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.

  • Olric

    Distributed in-memory object store. It can be used as an embedded Go library and a language-independent service.

    • Project mention: Olric: Distributed, embeddable in-memory data structures in Go | news.ycombinator.com | 2024-02-05

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo

  • redka

    Redis re-implemented with SQLite

    • Project mention: Redis Re-Implemented with SQLite | news.ycombinator.com | 2024-04-14

    I've decided to use the max connections approach for now.

    [1]: https://github.com/nalgeon/redka/blob/main/internal/sqlx/db....

  • pogreb

    Embedded key-value store for read-heavy workloads written in Go

    • Project mention: Sparkey is a simple constant key/value storage library | news.ycombinator.com | 2024-01-04

  • redix

    a very simple pure key => value storage system that speaks Redis protocol with Postgres as storage engine and more

  • IceFireDB

    @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.

  • gokv

    Simple key-value store abstraction and implementations for Go (Redis, Consul, etcd, bbolt, BadgerDB, LevelDB, Memcached, DynamoDB, S3, PostgreSQL, MongoDB, CockroachDB and many more)

    • Project mention: Map of Golang Key Value Engines | news.ycombinator.com | 2024-01-21

    Really great overview!

    I've been tracking some of them for a while as part of evaluating which ones to add to my key-value abstraction library gokv [1], but others only noticed recently. It's really interesting that there's no single most popular implementation, but new ones emerging and gaining popularity regularly.

    [1] https://github.com/philippgille/gokv

  • flashdb

    FlashDB is an embeddable, in-memory key/value database in Go (with Redis like commands and super easy to read) (by arriqaaq)

  • barreldb

    A disk based KV store (based on Bitcask implementation)

  • sdb

    SDB ：纯 Go 开发、数据结构丰富、持久化、简单易用的 NoSQL 数据库 (by yemingfeng)

  • badger

    Fast Key-Value DB in Go (by outcaste-io)

  • go-mcache

    Fast in-memory key:value store/cache with TTL

  • redhub

    High-performance Redis-Server multi-threaded framework, based on rawepoll model.

  • vkv

    vkv enables you to list, compare, move, import, document, backup & encrypt secrets from a HashiCorp Vault KV engine

  • microblob

    Serve millions of JSON documents via HTTP.

  • regatta

    Regatta is a distributed key-value store. It is Kubernetes friendly with emphasis on high read throughput and low operational cost.

  • kivi

    Dynamo-inspired distributed leader-less key-value database that has no unique features and no apparent reason to exist

  • gocask

    Go implementation of Bitcask - A Log-Structured Hash Table for Fast Key / Value Data

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020).

Go Key-Value related posts

Index

What are some of the best open-source Key-Value projects in Go? This list will help you:

Project Stars
1 etcd 46,505
2 badger 13,437
3 immudb 8,499
4 buntdb 4,401
5 rosedb 4,378
6 nutsdb 3,305
7 Olric 3,013
8 redka 2,691
9 pogreb 1,235
10 redix 1,196
11 IceFireDB 1,080
12 gokv 677
13 flashdb 343
14 barreldb 152
15 sdb 137
16 badger 127
17 go-mcache 93
18 redhub 77
19 vkv 76
20 microblob 66
21 regatta 61
22 kivi 39
23 gocask 33

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com