Hyperstage combines the Hyperstage storage engine with MySQL server implementation. Hyperstage consists of several layers. The upper layers are provided by the MySQL server implementation, and the lower layers are provided by Hyperstage.

Hyperstage includes both its own optimizer and executor along with the storage engine. The MySQL query engine can be used with Hyperstage. However, since the MySQL storage engine interface is row oriented, it cannot take full advantage of the column orientation or the Knowledge Grid and hence query execution through this path is reduced. Queries will be directed to the Hyperstage optimizer whenever possible.

Hyperstage ships with the full MySQL binaries required, including the MyISAM storage engine. MyISAM is used to store catalog information (as with other storage engines). You can use the MyISAM instance for other purposes, but joining MyISAM and Hyperstage tables may result in reduced performance as the MySQL query engine will be used.

MySQL provides:

• Mature connectors, tools and resources.
• Interconnectivity and certification with BI tools.
• Management services and utilities.

Hyperstage provides:

• Load function that compresses data.
• Column-oriented storage engine.
• Knowledge Grid metadata layer that contains information about the compressed data.
• Optimizer/executor that uses the Knowledge Grid.

Since other storage engines, like InnoDB and Falcon, are not included in the Hyperstage distribution, they must be run as separate instances (executables). If you wish to combine other storage engines with Hyperstage, you will need to look at a database federation application (some BI tools provide this).