yottaStore
A datastore aiming at linear scalability up to the yottabyte range. Inspired by dynamo and cassandra. (by yottaStore)
pebble
RocksDB/LevelDB inspired key-value database in Go (by cockroachdb)
| yottaStore | pebble | |
|---|---|---|
| 9 | 11 | |
| 79 | 4,455 | |
| - | 1.2% | |
| 1.8 | 9.8 | |
| about 1 year ago | 5 days ago | |
| Go | ||
| MIT License | BSD 3-clause "New" or "Revised" 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.
yottaStore
Posts with mentions or reviews of yottaStore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-16.
- Ask HN: Why are there no open source NVMe-native key value stores in 2023?
-
How to deal with overflowing counters?
I'm building a database, and I'm working on the storage format. For each record I have a logical clock which increases by 1 every time there's a write operation on the record, and I would like to be able to compare the clocks of two writes to understand which happened first.
-
Need help porting a wait free trie from C to Rust (and other silly questions)
If you're curious to know more, the tree is used for rendezvous based routing, as used by my datastore. I'm doing machine learning on a 200 TB dataset, using around 200 machines.
-
Looking for fast, space-efficient key-lookup
I copied this approach from several papers, with some improvements, for my datastore.
-
How to handle hundreds of routes?
I have a server with hundreds of routes, representing all the possible operations I can do on a datastore. How can I organize my code better?
-
Async-rdma v0.4.0: A Rust lib for writing high-throughput, low-latency networking apps simply
Yes I'm building a database where storage and compute are decoupled. I use io_uring to do pseudo-RDMA, and I'm looking to add ePBF to make it even more effective.
-
Avoid hash flooding without a secret key?
I'm currently building an implementation of the dynamo paper, yottastore. Imagine it as a huge, distributed, hash map.
-
How to deal with a very big hash table?
I'm building an implementation of the dynamo paper, yottastore. Given a key, I need to find which NVMe block stores the data. To do that I hash the key to find the shard where I have an in memory array in which at position [hash] I can find a struct with:
-
Golang is better than Rust for next generation in-memory database
I have to be honest, I'm very skeptical about your results and your code. I'm building a database, yottastore, both in javascript, golang and rust so I think I can share my opinion:
pebble
Posts with mentions or reviews of pebble.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-12.
- Fivefold Slower Compared to Go? Optimizing Rust's Protobuf Decoding Performance
-
Hummock: A Storage Engine Designed for Stream Processing
To improve the compacting speed of L0 files, we took inspiration from the design of the CockroachDB storage engine pebble.
- RocksDB/LevelDB inspired key-value database in Go
-
Is there a lightweight, stable and embedded database library?
https://github.com/cockroachdb/pebble ?
-
Understanding Fantoms Underlying Tech & Lachesis Consensus Algorithm + The Most Recent Developments
Pebble is a LevelDB/RocksDB-inspired key-value database focused on performance. PebbleDB is replacing Fantom’s previous RPC software to match Fantom’s sheer throughput. PebbleDB is consistently faster than previous options and it has helped the Fantom network to consistently reach synchronization with the network quicker while reducing the duration of API requests.
-
Looking for fast, space-efficient key-lookup
https://github.com/cockroachdb/pebble Pure go SSD native key-value store. You could think of it as map[[]byte][]byte on persistent storage.
-
Open Source Databases in Go
Genji is a document-oriented, embedded, SQL database. It is build over Pebble which is a port of RocksDB in Go, by the authors of CockroachDB.
-
CockroachDB: The Resilient Geo-Distributed SQL Database
Out of curiosity, why write https://github.com/cockroachdb/pebble and not just use https://github.com/dgraph-io/badger?
- Recommendation for Key/Value storage
-
CGo-free sqlite database/sql driver 1.8.0 for darwin/amd64 released
There's the semi-recent pebble from the folks that make cockroach db. Haven't used it, but seems promising: https://github.com/cockroachdb/pebble
What are some alternatives?
When comparing yottaStore and pebble you can also consider the following projects:
solid_cache - A database-backed ActiveSupport::Cache::Store
bolthold - BoltHold is an embeddable NoSQL store for Go types built on BoltDB
async-rdma - Easy to use RDMA API in Rust async
LevelDB - LevelDB is a fast key-value storage library written at Google that provides an ordered mapping from string keys to string values.
cdb - A native golang implementation of cdb (http://cr.yp.to/cdb.html)
badger - Fast key-value DB in Go.
KVRocks - RocksDB compatible key value store and MyRocks compatible storage engine designed for KV SSD
pogreb - Embedded key-value store for read-heavy workloads written in Go
ssd-nvme-database - Columnar database on SSD NVMe
Redis - Redis Go client
uNVMe - KV and LBA SSD userspace NVMe driver
goleveldb - LevelDB key/value database in Go.