It is really important to be compatible with MySQL, which can greatly reduce resistance to adoption.
I miss the old days when everything gets into MySQL (even small images! Because backing up and restoring MySQL is easier than dealing with lots of small files)
When I am asked to set up a "BI", most of the time it is just a fancy word for "SQL Visualization". Being able to use the same language (SQL) throughout the whole pipeline is great. The boundary between OLAP & OLTP is kind of unclear. I like how TiDB's way of seeing it.
As a Chinese, I think this feature is quite useful for us.Though I use VPN most of the time, I do dislike being interrupted for several minutes when I accidentally searched some censored words.
I miss the old days when everything gets into MySQL (even small images! Because backing up and restoring MySQL is easier than dealing with lots of small files)
When I am asked to set up a "BI", most of the time it is just a fancy word for "SQL Visualization". Being able to use the same language (SQL) throughout the whole pipeline is great. The boundary between OLAP & OLTP is kind of unclear. I like how TiDB's way of seeing it.