Distributed SQL database (TiDB) source code explained

I am watching this project very closely. So far I think it has the potential to be a full featured replacement for FoundationDB. Note that they rewrote the underlying distributed, sorted, transactional KV store from Go to Rust which is the piece I am most interested in.

Within the spectrum of so-called &quot;NewSQL&quot; databases, there are basically two kinds:<p>* ones built on top of a mature relational database (e.g. Vitess, CitusDB)<p>* ones built on top of some custom or unproven KV store (e.g. TiDB, CockroachDB, NuoDB)<p>Ultimately, despite claims of benchmarks&#x2F;elegance&#x2F;MySQL not being web scale enough, I&#x27;m unsure if (at least in the immediate future) it&#x27;s a wise move to do the latter. Solutions that use a proven storage engine seem like an easier pill to swallow.

I&#x27;d be more interested to see some articles and posts on how to <i>use</i> TiDB and&#x2F;or TiKV in interesting ways.<p>There&#x27;s been plenty of explanation on how its built, their process, the architecture, etc. Some practical application would be helpful now to help contextualize those decisions.

I think TiKV on its own looks quite interesting. I see that the readme considers it to be part of TiDB, but I can see uses for TiKV on its own, without TiDB. Do you have anyone doing this in production?

This takes a lot of work to do, kudos! Don&#x27;t listen to any haters, this is the type of document you can use to reply to them. Great job, keep it up. Cheers! ~ A friendly distributed DB competitor