skytable VS kvrocks

Hey HN!

I've been working on Skytable since 2020 and after several iterations from a simple K/V store, we've walked the path to this release. The goal of Skytable is to deliver a solid foundation for building data intensive applications.

Skytable's primary goal is performance and scale. Even with a query language it can outperform K/V stores which use simple commands (benchmarks will be shared in another post).

Several implementations in Skytable (especially around query evaluation and execution) are fundamentally different from SQL and even NoSQL counterparts and there are some entirely new concepts which might make it a little hard to grasp.

BlueQL is a very important part of Skytable and it employs some interesting concepts to try and reduce the surface for injection attacks and tries to be a modern and secure alternative to SQL.

- Source code: https://github.com/skytable/skytable

For those who were looking for the source code, here's the link: https://github.com/skytable/skytable

Link to source code: https://github.com/skytable/skytable

Here are some quick links: - Source code: https://github.com/skytable/skytable - Rust driver: https://github.com/skytable/client-rust

I think this is relevant... These are 3 OSS databases that can be an alternative to Redis:

- KeyDB: https://github.com/snapchat/keydb

- Dragonfly: https://github.com/dragonflydb/dragonfly

- Skytable: https://github.com/skytable/skytable

I have used keyDB before. The raft consensus makes building an HA Redis easy.

:) in fact, I copied the definition from the project page and Skytable is not finished project yet. You can see here, the real time features in the road map. https://github.com/skytable/skytable/issues/203

I switched from SSDB to Kvrocks recently, because SSDB is abandoned and the author missing for 3 years now. I used to recommend SSDB, but now there's better alternatives available:

https://github.com/apache/kvrocks

https://github.com/sabledb-io/sabledb

Another under the radar Apache project I've found myself using is Apache KvRocks

https://github.com/apache/kvrocks

It's a Redis compatible database on top of RocksDB, so unlike Redis it uses the disk instead of RAM, but you can control how much data is cached in RAM, obviously Kvrocks will be slower than Redis for uncached data.

Useful in situations where you want a KV data store that isn't limited by your memory specs but is compatible with everything that speaks Redis.

There’s Kvrocks. It uses the Redis protocol and it’s built on RocksDB https://github.com/apache/kvrocks

Apache Kvrocks is a distributed key-value NoSQL database that uses RocksDB as a storage engine and is compatible with Redis protocol.

We use Kvrocks[0] at work. It is Redis on disk, powered by "RocksDB" (hence the name) and compatible with most of the Redis clients since it respects the Redis protocol. It was incubated by Apache earlier this year.

It works great and the development is really active.

[0]: https://kvrocks.apache.org