ClustrixDB uses MySQL syntax but was built from the ground up to be a distributed, shared-nothing database. Any application that uses a MySQL client or JDBC/ODBC drivers, like Ruby on Rails or Hibernate, can connect to ClustrixDB without issue and use standard MySQL constructs to interact with ClustrixDB. The following sections describe ClustrixDB-specific syntax and caveats for MySQL compatibility.
ClustrixDB aims to provide support for most standard MySQL functionality. While we do not synchronize our feature development with MySQL releases, we strive to provide the features and functions required by our customers to successfully run production environments. We monitor both our customers' requirements and new MySQL functionality to determine our feature roadmap and use recent shipping releases of MySQL as part of an automated QA process for compatibility.
ClustrixDB is a clustered, distributed database built from the ground up for scale, concurrency, and performance as well as ease of use. While ClustrixDB seeks to be MySQL compatible, it contains no actual MySQL source code.
Here is more on ClustrixDB internals:
ClustrixDB most closely matches the InnoDB storage engine. All tables in ClustrixDB are fully transactional and ACID-compliant and use the MVCC model for concurrency control. For compatibility purposes, the default engine type is listed as InnoDB but the Clustrix engine type is applied. Clustrix also accepts syntax for setting the engine type to ndb, ndbcluster, myisam, mrg_mysisam but the Clustrix engine is always used.
For additional information on ClustrixDB and MySQL Compatibility, please see one of the following pages: