HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pingcap
tiflash
C++2022–2022
pingcap / tiflash

tiflash

The analytical engine for TiDB and TiDB Cloud. Try free: https://tidbcloud.com/free-trial

5Distinct people
5Mentions
0Explicit recommenders
1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The analytical engine for TiDB and TiDB Cloud. Try free: https://tidbcloud.com/free-trial

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2022-03-25 09:23:53 UTC to 2022-06-04 19:08:34 UTC. Weeks start Monday, UTC.

012022-03-21 00:00:00 UTC to 2022-03-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 212022-03-28 00:00:00 UTC to 2022-04-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-04-04 00:00:00 UTC to 2022-04-11 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-04-11 00:00:00 UTC to 2022-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-18 00:00:00 UTC to 2022-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-25 00:00:00 UTC to 2022-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 252022-05-02 00:00:00 UTC to 2022-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-09 00:00:00 UTC to 2022-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-16 00:00:00 UTC to 2022-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-23 00:00:00 UTC to 2022-05-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-05-30 00:00:00 UTC to 2022-06-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 212022-03-21 00:00:00 UTC2022-03-28 00:00:00 UTC110
Mar 282022-03-28 00:00:00 UTC2022-04-04 00:00:00 UTC110
Apr 42022-04-04 00:00:00 UTC2022-04-11 00:00:00 UTC110
Apr 112022-04-11 00:00:00 UTC2022-04-18 00:00:00 UTC000
Apr 182022-04-18 00:00:00 UTC2022-04-25 00:00:00 UTC000
Apr 252022-04-25 00:00:00 UTC2022-05-02 00:00:00 UTC000
May 22022-05-02 00:00:00 UTC2022-05-09 00:00:00 UTC000
May 92022-05-09 00:00:00 UTC2022-05-16 00:00:00 UTC000
May 162022-05-16 00:00:00 UTC2022-05-23 00:00:00 UTC000
May 232022-05-23 00:00:00 UTC2022-05-30 00:00:00 UTC101
May 302022-05-30 00:00:00 UTC2022-06-06 00:00:00 UTC101

What Hacker News says

5 sources
One of the founder of TiDB/TiKV here from PingCAP (https://pingcap.com) I have been thinking about this problem with my peers when I started to build TiDB (https://github.com/pingcap/tidb) seven years ago. At that time, nearly all of us were familiar with Go language, so we decided to use Go to build the SQL layer of TiDB. Thanks to Go, we could develop TiDB very quickly and released the first MVP in half a year. I remembered clearly the sense when we ran TPC-C successfully, although the TPMC was just 1 at that time, this was a good start for us. But Go had some problems, e.g. the GC was not good before, the fair scheduling might cause some latency problem, or data racing may happen sometimes. So when we decided to build a distributed storage (aha, TiKV (https://githbu.com/tikv/tikv), we wanted use another language to guarantee safety. I
Read the rest
really admire our courage - we chose Rust which was just released 1.0 and missed lots of libraries at that time. Now it seems that this is an awesome choice, TiKV has been graduated from CNCF, and been used as building block not only for TiDB, but also for other distributed systems. Thanks Rust. When TiDB started being used in many companies, we found that our customer not only ran lots of online transactions in TiDB, but also they wanted to ran some realtime analytic queries directly because the data has been in TiDB already. So we decided to build a HTAP database, to introduce a column storage beside TiKV, this is TiFlash (https://github.com/pingcap/tiflash). We build TiFlash based on Clickhouse, so of course, we use C++. As you can see, to build only one integrated database - TiDB, we at least use three languages, every language has its own reason to be introduced. We can treat the distributed database as a service system, each service can be built with your favorite language and the services are linked by gRPC like TiDB does now. You may doubt that - “hey, guys, you are building a database, performance is very importance”. Yes, this is true, but we also build a complex distributed system, especially on the cloud. Scale-out, elastic, user experience must be important too. This is trade off for an engineer :-)
In [dead]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.