qiuyesuifeng

In this paper, we propose a novel solution, called Passive Data Persistence Scheme (PASV), to address the double-logging problem in LSM-tree based RDBs.

It's really hard for those startups in this status...

An interesting program BenchBase is a multi-threaded load generator. The framework is designed to be able to produce variable rate, variable mixture load against any JDBC-enabled relational database. The framework also provides data collection features, e.g., per-transaction-type latency and throughput logs.

An overview of how we think about speed, covering ways our customers power timely business workflows, the typical speeds they experience and improvements we are making to speed up Reverse ETL for everyone.

An architecture of having both row-based database and column-based data might also be interesting to explore. This post explains how they work together. https://pingcap.com/blog/delivering-real-time-analytics-and-...

TiDB has already supported this (similar) feature about 2 years ago and it has been adopted by the gaming users: https://www.pingcap.com/blog/2016-11-15-Travelling-Back-in-T...

This is a fairly good point. Personally, I believe this also opens a debate about open source software VS proprietary software. Customers of proprietary software companies usually have minimal influence on the priorities and timelines of where/when the product is going. Not to mention the opacity which makes it unable to modify the code or debug it effectively. Most of the time when an issue occurs, you are faced with unclear error codes/messages/documents. If there is no existing workaround or patch, you have to wait until your issue climbs up to the top of the vendor's priority list. Whereas in the open source community, many eyes are examing the source code and many hands (including yourself) are ready to jump in all the time, making it more possible that more bugs are exposed and quicker to get a fix or workaround.

If you are open to trying other options, TiDB (https://github.com/pingcap/tidb) is also a good choice. A use case is just published on Datanami today: https://www.datanami.com/2018/02/22/hybrid-database-capturin...