corobase
ScaleStore
corobase | ScaleStore | |
---|---|---|
1 | 2 | |
228 | 108 | |
0.0% | 3.7% | |
0.0 | 3.4 | |
over 2 years ago | 3 months ago | |
C++ | C++ | |
MIT License | MIT License |
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.
corobase
ScaleStore
-
Ask HN: Why are there no open source NVMe-native key value stores in 2023?
I don't remember exactly why I have any of them saved, but these are some experimental data stores that seems to be fitting what you're looking for somewhat:
- https://github.com/DataManagementLab/ScaleStore - "A Fast and Cost-Efficient Storage Engine using DRAM, NVMe, and RDMA"
- https://github.com/unum-cloud/udisk - "The fastest ACID-transactional persisted Key-Value store designed for NVMe block-devices with GPU-acceleration and SPDK to bypass the Linux kernel."
- https://github.com/capsuleman/ssd-nvme-database - "Columnar database on SSD NVMe"
-
The end of a myth: Distributed transactions can scale
The linked blog post at the top of this article - https://muratbuffalo.blogspot.com/2023/01/is-scalable-oltp-i... - provides graphics that give extremely useful context. And here's the repo for the paper that discusses: https://github.com/DataManagementLab/ScaleStore
The idea that one of many writer-compute-nodes can literally reach into a memory buffer that is shared across machines, atomically flip some lock bits and propagate some cache-coherence messages, and use that to build a multi-writer distributed database without needing to partition (and where any writer-compute-node can handle any message, so you can just round-robin a firehose of messages at them)... and that there's a chance (though not yet implemented) that one could implement ACID on top of this? It's absolute madness, and wildly exciting.
What are some alternatives?
qcoro - C++ Coroutines for Qt
solid_cache - A database-backed ActiveSupport::Cache::Store
Forkpool - A bleeding-edge, lock-free, wait-free, continuation-stealing tasking library. [Moved to: https://github.com/ConorWilliams/libfork]
ssd-nvme-database - Columnar database on SSD NVMe
libcoro - C++20 coroutine library
KVRocks - RocksDB compatible key value store and MyRocks compatible storage engine designed for KV SSD
stonedb - StoneDB is an Open-Source MySQL HTAP and MySQL-Native DataBase for OLTP, Real-Time Analytics, a counterpart of MySQLHeatWave. (https://stonedb.io)
Olric - Distributed in-memory object store. It can be used as an embedded Go library and a language-independent service.
uNVMe - KV and LBA SSD userspace NVMe driver
KVSSD - KV SSD host software including APIs and drivers
NebulaGraph Database - A distributed, fast open-source graph database featuring horizontal scalability and high availability
udisk - The fastest ACID-transactional persisted Key-Value store designed as modified LSM-Tree for NVMe block-devices with GPU-acceleration and SPDK to bypass the Linux kernel