HackerTrans
TopNewTrendsCommentsPastAskShowJobs

std_reply

no profile record

comments

std_reply
·9 tháng trước·discuss
Using Python syntax makes it more accessible.
std_reply
·2 năm trước·discuss
Have you looked at tiup?

https://tiup.io
std_reply
·2 năm trước·discuss
EDB Distributed Postgres under the hood is a single node database with bolted on replication.
std_reply
·2 năm trước·discuss
I’m contrasting a single node database with bolted on replication vs a distributed SQL database that gives strong consistency out of the box.
std_reply
·2 năm trước·discuss
Go is used for the SQL layer, it’s a modern optimizer that can do distributed joins etc. ie. Issue parallel reads to the storage nodes.

Additionally, it can push down the DAG to the TiKV storage nodes, written in Rust, to reduce movement of data and work closer to the physical data.
std_reply
·2 năm trước·discuss
I would argue the opposite, distributed databases are much easier to operate at large scale. Truly online distributed DDL, at least in TIDB, strong consistency etc.

People who bang on about Postgres replication have rarely setup replication in Postgres themselves and that too in the 100a of Pb scale.

MySQL replication works well and can be scaled more easily (relative to Postgres) but has its own problems. eg., DDL is still a nightmare, lag is a real problem, usually masked by async replication. But then eventual consistency makes the application developers life more complicated.
std_reply
·2 năm trước·discuss
TiKV the Core Storage scalable component is a CNCF graduated projected. PingCAP cannot change the license even if it wanted to.
std_reply
·2 năm trước·discuss
TiDB is running core banking services too.

I think people’s idea of scale and operating at scale is limited to their experience.

You can get MySQL to run at any scale, look at Meta and Shopify. Operational complexity at that scale is a different story.

Distributed databases reduce a lot of the operational complexity. To take one example:

Try a DDL on a 5 TB table in any replicated MySQL topology of choice and compare it with TiDB’s Distributed execution framework.
std_reply
·2 năm trước·discuss
This is quite an ignorant comment. TiDB routinely handles 100s of TB of data. Go watch LinkedIn’s presentation on why they choose TiDB as their strategic db going forward.
std_reply
·2 năm trước·discuss
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