yottaStore
A datastore aiming at linear scalability up to the yottabyte range. Inspired by dynamo and cassandra. (by yottaStore)
goleveldb
LevelDB key/value database in Go. (by syndtr)
| yottaStore | goleveldb | |
|---|---|---|
| 9 | 15 | |
| 79 | 6,025 | |
| - | - | |
| 1.8 | 0.0 | |
| about 1 year ago | 5 months ago | |
| Go | ||
| MIT License | BSD 2-clause "Simplified" 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:
goleveldb
Posts with mentions or reviews of goleveldb.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-12.
-
Looking for fast, space-efficient key-lookup
Looks like a job for GoLevelDB.
-
Open Source Databases in Go
goleveldb - Implementation of the LevelDB key/value database in Go.
- A Database for 2022
-
An IndexedDB clone in pure Go
I wanted to get deeper insights into both indexeddb and leveldb, so decided to write an indexeddb wrapper around goleveldb.
-
What type of software do you write at your workplace?
https://github.com/syndtr/goleveldb for heavy-duty local data storage.
-
Embedded write-heavy on-disk cache, write-amplification
We're using go-leveldb for a reasonably high-load case here at my $dayjob.
-
Best way to store logs?
I would used some embedded kv store like go-leveldb or bolt. Key is BigEnding timestamp + optional tail to allow duplicate timestamps.
-
Memory leack (?) with pprof on graphql server
I'm using the leveldb https://github.com/syndtr/goleveldb for the moment because I'm developing the architecture. Mh, leveldb support the only the inmem db? :/
- IceFireDB：Distributed disk storage database based on Raft and Redis protocol.
- https://np.reddit.com/r/programming/comments/p7a56u/icefiredbdistributed_disk_storage_database_based/h9i9j44/
What are some alternatives?
When comparing yottaStore and goleveldb you can also consider the following projects:
solid_cache - A database-backed ActiveSupport::Cache::Store
badger - Fast key-value DB in Go.
async-rdma - Easy to use RDMA API in Rust async
bolt
cdb - A native golang implementation of cdb (http://cr.yp.to/cdb.html)
bbolt - An embedded key/value database for Go.
KVRocks - RocksDB compatible key value store and MyRocks compatible storage engine designed for KV SSD
buntdb - BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support
ssd-nvme-database - Columnar database on SSD NVMe
Tile38 - Real-time Geospatial and Geofencing
uNVMe - KV and LBA SSD userspace NVMe driver
kingshard - A high-performance MySQL proxy