tikv
KeyDB
Our great sponsors
| tikv | KeyDB | |
|---|---|---|
| 21 | 24 | |
| 14,476 | 10,600 | |
| 1.7% | 18.4% | |
| 9.7 | 8.4 | |
| 1 day ago | 2 days ago | |
| Rust | C++ | |
| Apache License 2.0 | BSD 3-clause "New" or "Revised" 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.
tikv
-
just wanted to ask is there an in memory database that uses s3 or gcp cloud storage as permanent storage
I know that very similar functionality to this is in TiDB Serverless ( https://tidbcloud.com ). TiDB is a distributed relational database. It uses TiKV ( which is a key/value engine ) as the storage engine. You could use SQL to access your K/V records. There is ongoing work in TiKV to support S3 directly as the storage backend ( https://github.com/tikv/tikv/issues/6506 ) .
- Implementing a distributed key-value store on top of implementing Raft in Go
- Production grade databases in Rust
- Can anyone recommend tikv nosql database
- Go devs that learned Rust, what are your thoughts on it?
-
Apache Pegasus – A a distributed key-value storage system
TiKV is basically a layer on top of rocksdb https://github.com/tikv/tikv/blob/956610725039835557e7516828...
- TiKV is a highly scalable, low latency, and easy to use key-value database
-
Surrealdb – FOSS document-graph database, for the realtime web in Rust
> Many,many smart people…
If you look inside the code you can see the stated features are a result of underlying engine (TiKV [0] also in c and rust from pingcap). Surrealdb is standing on shoulders of giants at present, they are TiKV, FoundationDB and rocksdb. The feature set they mentioned mostly coming from TiKV at present.
-
Cloud database for tomorrow's applications (written in Rust)
Hi Diggsey, great question. We are currently focussed on functionality and stability, and then will draw our attention to performance. Coming this week we have a RocksDB storage implementation. We've only just launched our initial beta version, and we know there is a lot of improvement and work to be done (some of these performance issues we know about already and are on our Github issues list).
With regards to the consistency/isolation model, SurrealDB sits on top of a number of key-value stores. By using the distributed highly-available TiKV storage backend, https://tikv.org, (and we have a FoundationDB integration in the works), the database is designed to be highly-scalable and highly-available. The same guarantees (albeit just single-node, so no high-availability or scalability) will be available with the RocksDB implementation coming this week. By sitting on top of these key-value stores, SurrealDB ensures that all transactions are ACID compliant. We don't want to go for speed (for instance by writing to /dev/null) over anything, but want SurrealDB to be a reliable and performant backend for any application. Obviously we have a way to go to catch up with PostgreSQL (launched in 1996), but we will strive to get there!
-
CeresDB: A high-performance, distributed, schema-less and time-series database
If you are looking for a production ready distributed store written in Rust. Check out TiKV(https://github.com/tikv/tikv), which was also mentioned in the acknowledge section of the project's README.
There's also a full-featured distributed RDBMS called TiDB built on top of TiKV.
KeyDB
-
Redict 7.3.0, a copyleft fork of Redis, is now available
Three. KeyDB forked before the recent shake-up.
-
KeyDB: A Multithreaded Fork of Redis
Can you explain what lead you to believe it's dead?
Looking at the Issues in their Github, a couple of days ago they mentioned to be working on some features in a branch.
https://github.com/Snapchat/KeyDB/issues/798#issuecomment-20...
-
Redict is an independent, copyleft fork of Redis
https://github.com/Snapchat/KeyDB
KeyDB is an existing fork that’s well supported and has a solid community for those interested. It takes a different philosophy to Redis but can be a drop in replacement in many cases
- KeyDB – A Multithreaded Fork of Redis
- Redis License Changed
- [BUG] Address is used after it has been freed (dict).
-
The first version of Redis, written in Tcl
To me it's still not clear if 6.3.x is stable (https://github.com/Snapchat/KeyDB/issues/494) and performant (https://github.com/Snapchat/KeyDB/issues/470).
-
Migrating from Redis to KeyDB
I posted about KeyDB, a multi-threaded fork of Redis, here already a while ago. We still use it in some cases and find it beneficial.
- Snapchat/KeyDB: A Multithreaded Fork of Redis
What are some alternatives?
redis-rs - Redis library for rust
dragonfly - A modern replacement for Redis and Memcached
rust-etcd - An etcd client library for Rust.
keydb-operator - A KeyDB (Drop-In Alternative to Redis) Operator for Kubernetes, based on Ansible Operator SDK.
rust-rocksdb - rust wrapper for rocksdb
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
cassandra-rs - Cassandra (CQL) driver for Rust, using the DataStax C/C++ driver under the covers.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
rust-postgres - Native PostgreSQL driver for the Rust programming language
skytable - Skytable is a modern scalable NoSQL database with BlueQL, designed for performance, scalability and flexibility. Skytable gives you spaces, models, data types, complex collections and more to build powerful experiences
diesel - A safe, extensible ORM and Query Builder for Rust
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.