tikv VS Parity

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 ) .

TiKV is basically a layer on top of rocksdb https://github.com/tikv/tikv/blob/956610725039835557e7516828...

> 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.

[0] https://tikv.org/

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!

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.

What got me interested in learning Rust with Ethereum is Reth (Rust Ethereum Execution Layer Client). OpenEthereum was another Rust client that got deprecated earlier in 2022, which is what I think inspired Reth to be made https://github.com/openethereum/openethereum . It sounds like Reth will go live in January/February 2023 https://github.com/paradigmxyz/reth#status they put out a summary here too https://www.paradigm.xyz/2022/12/reth

OpenEthereum | Programming Language = Rust

OpenEthereum v3.2.0 is ready for Berlin.

It's still maintained https://github.com/openethereum/openethereum

For Ethereum, there is Geth, OpenEthereum, Nethermind, among others.

I'm not sure why this was linked. Parity decided to stop developing their Ethereum client and this repo has been sitting unmaintained for about 2 years now, it will almost certainly not successfully sync with mainnet.

The Parity codebase was taken over by new maintainers and turned into OpenEthereum: https://github.com/openethereum/openethereum

However, writing and maintaining an Ethereum client is an exceptional amount of work with very little benefit, the primary OpenEthereum maintainers recently announced they would stop maintaining OpenEthereum and would start pouring their energies into an upcoming client called Erigon. https://medium.com/openethereum/gnosis-joins-erigon-formerly...

Erigon is a much better client.

Also, the Ethereum Foundation doesn't own a lot of the code used in the network. For example, lots of people use OpenEthereum as their client, which is not managed by EF.