Xpand built from the ground up to be a distributed, shared-nothing database and does not have any source code from other projects in its code base. Any application that uses a MySQL client or JDBC/ODBC drivers (e.g. Ruby on Rails or Hibernate) can connect to Xpand without issue and use standard MySQL constructs to interact with Xpand.
|Number of Tables||Xpand supports a maximum of approximately 2,000 tables. The precise limit for your installation depends on the number and type of indexes.|
|Number of Columns||Xpand recommends that each table have no more than 200 columns (including system-defined hidden columns), as higher column counts can impact performance and scalability.|
|Row Size||In Xpand, the maximum row size for persistent tables (stored on disk) is 64MB. The maximum row size when using RBR replication is 32MB.|
The maximum length for object names is 64 characters, which matches MySQL.
On Xpand, object name comparisons are case insensitive and table names are stored in the case specified in the CREATE statement. The lower_case_table_names global variable has a value of 1 and cannot be changed.
The following are reserved keywords for Xpand but not MySQL:
Xpand is a clustered, distributed database built from the ground up for scale, concurrency, and performance as well as ease of use. While Xpand seeks to be MySQL compatible, it contains no actual MySQL source code.
Here is more on Xpand internals: