TiDB – A distributed NewSQL database compatible with MySQL protocol
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderWonder how this compares to ActorDB http://www.actordb.com/
So a SQL layer on top of a KV base? Isn't this very similar to what FoundationDB did (and had a lot of trouble with)? if so, good post by John Hugg of voltdb about it: http://voltdb.com/blog/foundationdbs-lesson-fast-key-value-s... How does tiDB compare to this?
TiDB has four main components: 1. SQL front end nodes 2. Distributed shared nothing storage (TiKV) 3. Meta data server (PS) 4. TiFlash column store 1 and 3 are written in Go 2 is written in Rust and uses RocksDB 4 is written in C++ 2 & 3 are graduated CNCF projects maintained by PingCAP. Disclaimer: I work for PingCAP
How fast is it? SQL on top of KV is tough to make zippy due to metadata and scanning issues.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 322
- Total comments
- 133
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking