“Regatta’s fractured mirrors can maintain multiple copies of the same table(s), possibly in different sets of nodes inside the cluster. This allows the same data to be represented differently among various mirrors. This allows physical separation of data and compute between operational transactions and analytics, effectively eliminating any impact of analytical workloads on the transactional performance. While the mirror for transactional operations is organized as a row-store, the mirror for analytics purposes can be organized as either a row-store or a column-store. Regatta guarantees high performance and data currency – for both types of stores, at all times. When a column-store is used as a fractured mirror of a row-store that is used for transactional operations, Regatta’s proprietary technology for fractured-mirror updating enables both the row store and the column store to be completely up-to-date, at all times, without degrading OLTP performance.”
Maybe take a look at Regatta
Looks great:
“Regatta’s fractured mirrors can maintain multiple copies of the same table(s), possibly in different sets of nodes inside the cluster. This allows the same data to be represented differently among various mirrors. This allows physical separation of data and compute between operational transactions and analytics, effectively eliminating any impact of analytical workloads on the transactional performance. While the mirror for transactional operations is organized as a row-store, the mirror for analytics purposes can be organized as either a row-store or a column-store. Regatta guarantees high performance and data currency – for both types of stores, at all times. When a column-store is used as a fractured mirror of a row-store that is used for transactional operations, Regatta’s proprietary technology for fractured-mirror updating enables both the row store and the column store to be completely up-to-date, at all times, without degrading OLTP performance.”