tikv VS diesel

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.

Fair enough. Indeed I didn't consider support costs. Thank you for your answer!

Actually let me ask another thing. Your FAQ mentions you're considering hosting CockroachDB as a drop-in distributed replacement for PostgreSQL [0], and also you currently offer a distributed, eventually consistent PostgreSQL replication solution [1].

Is either Tikv [2] (distributed key-value store) or Tidb [3] (distributed database with a mysql interface, built on top of Tikv) on your radar?

You already offer Redis as a key-value store, but Tikv has an amazing property: it ensures strong consistency globally (not eventual consistency). Tidb, being built on top of Tikv, also has strong consistency.

[0] https://fly.io/blog/fly-answers-questions/#q-what-is-fly-doi...

[1] https://fly.io/blog/globally-distributed-postgres/

[2] https://github.com/tikv/tikv

[3] https://github.com/pingcap/tidb

tikv — A distributed KV database in Rust

TiKV: basis data key-value transaksional yang terdistribusi.

Before I introduce this phase, I'd like to talk about the batch system. It is the cornerstone of TiKV's multi-raft implementation.

TiKV is a distributed key-value storage engine, which is based on the designs of Google Spanner, F1, and HBase. However, TiKV is much simpler to manage because it does not depend on a distributed file system.

diesel

Congratulations to the release. I know all of this is hard work. I would like to invite you to submit a ormlite implementation to the diesel benchmark collection. As soon as that's merged you will get regular reports here. The relevant code is here in the diesel repository.

Doing arbitrary syntax transformations in procedural macros is not powerful enough? Does C++ have something like serde or diesel?

I've been building a relatively small project with axum and diesel, and I'm pretty happy with it.

There's also Diesel and SeaORM for higher level interfaces.

diesel rs: https://diesel.rs/

For connecting and performing queries on the db, I prefer diesel.

It's not even a libpq issue, but an issue with a specific libpq distribution. You just need to use a not broken version of libpq or ask the vendor of that specific libpq version to fix their binary. See here for a in depth discussion. Calling diesel or libpq to be responsible for this is rather strange.

Diesel is a Safe, Extensible ORM and Query Builder for Rust diesel-async is an pure rust fully async connection implementation for Diesel. It provides connection implementations for the Diesel PostgreSQL and MySQL backend. It is designed to be used as drop in replacement for the sync connection implementations in Diesel. diesel-async support almost all the functionality provided by diesel (beside migrations), so it features the same compile time guarantees as Diesel itself. It reuses Diesels query builder infrastructure here.