Though StoneDB V1.0 provides inspiring performance, it still has some drawbacks that are rooted in its design, including long execution time for TPC-H query 16, unsatisfying performance in processing transactional workloads, and comparatively long latency in populating latest changes to analytics workloads.

Therefore, we are redesigning StoneDB to eliminate these problems in our next version — StoneDB V2.0. StoneDB V2.0 will be based on MySQL 8.0. It aims to achieve at least 10 times higher query performance on TPC-H than that of V1.0, with a more concise architecture and a query optimizer that can intelligently offload query workloads to corresponding storage engines.

The design philosophy of StoneDB V2.0 is modularity and performance-cost balance. The following outlines the new features that will be implemented in StoneDB V2.0. To learn details about each feature, see the relevant chapter.

StoneDB V2.0 will still be an open source project, which is a counterpart of close source service, MySQL Heatwave.

At first, an in-memory column-based engine (IMCE) will be used. Secondly, a cost-based query engine will be developed to automatically offload transactional and analytics workloads. Thirdly, StoneDB V2.0 will provide a vectorized execution engine and support massive parallel processing. In this way, the execution performance of StoneDB V2.0 will be at least ten times as that of StoneDB V1.0.

StoneDB will load the data into memory from InnoDB, just the same as MySQL Heatwave.