by std_reply on 1/7/25, 12:27 AM
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
by eikenberry on 1/6/25, 10:58 PM
VC backed database company with a CLA on their "open source" project. Red flag.
Is there a community fork yet?
by srameshc on 1/6/25, 10:17 PM
I love these new distributed DBs. CockroachDB is one of them. Still I think a managed Postgres/MySQL is a better choice. My primary concern is how challenging will it be if you have to eventually move your data out to a RDBMS for cost or other reasons. Does anyone have any experience ? I am not talking enterprise scale but data about size of 50 - 100GB scale.
by oa335 on 1/7/25, 12:31 AM
by otterley on 1/6/25, 9:54 PM
TiDB is 8 years old now; what's new?
by willvarfar on 1/6/25, 9:57 PM
Hardly hear about TiDB. How is it faring and how does it stack up to more well know competition?
by peterson_lock on 1/6/25, 9:49 PM
by nuphonenuacc on 1/7/25, 12:15 AM
What is that first paragraph? "This implementation proves the CAP theorem as wrong"? Doesn't tell me what your drawbacks are. This is mongodb all over again. Will only ever consider if the customer really wants it. (My guess performance)
(Also, bold move to write a db without fully being able to manage memory).
by geenat on 1/7/25, 4:45 PM
Not having a single binary distribution like CockroachDB is hurting adoption of TiDB.
by tonymet on 1/7/25, 1:09 AM
Does "cloud native" mean "has kubernetes config" or is there something else to it?