Xpand Storage Engine
Topics on This Page:
MariaDB Xpand provides distributed SQL, high availability, fault tolerance, write scaling, and horizontal scale-out for transactional workloads. MariaDB Xpand can integrate with the Xpand storage engine in MariaDB Enterprise Server 10.5.
Overview
Xpand provides distributed SQL.
Xpand integrates with the Xpand storage engine in MariaDB Enterprise Server 10.5:
Xpand supports transactional workloads.
Xpand is strongly consistent.
Xpand leverages a shared-nothing architecture to efficiently execute distributed SQL.
Xpand provides high availability (HA) and fault tolerance by design.
Xpand scales out horizontally for both reads and writes.
Note
Want to use MariaDB Xpand immediately? Get Started with MariaDB Xpand.
Xpand Versions
Available MariaDB Xpand versions are listed below:
Release Date |
Version |
|---|---|
2021-03-15 |
|
2021-03-08 |
|
2020-12-14 |
The listed MariaDB Xpand versions can be used in both the Xpand Performance topology and the Xpand Storage Engine topology.
Enterprise Server Versions
MariaDB Xpand is compatible with the Xpand storage engine included with MariaDB Enterprise Server:
Xpand Version |
Compatible ES Version(s) |
|---|---|
The listed MariaDB Enterprise Server versions can be used in the Xpand Storage Engine topology.
Feature Summary
Xpand storage engine has the following features:
Workload Optimization: Distributed SQL
Table Orientation: Row
ACID Compliant: Yes
SQL Features: Primary Keys, AUTO_INCREMENT, Foreign Keys, Indexes, Unique Indexes, Online Schema Changes, Lockless Reads, Row Locks
High Availability: Yes
Multi-Version Concurrency Control (MVCC): Yes
More information about features can be found at MariaDB Xpand.
Deployment Instructions
To deploy MariaDB Xpand, choose a topology:
Topology |
Description |
|---|---|
|
|
|
For additional information, see "Deploy Xpand 5.3".
Term Definitions
Term |
Definition |
|---|---|
Node |
One service on a system. |
Plugin |
A component of MariaDB Enterprise Server which may be included in the server function optionally, either at runtime or compile-time, and which adheres to an established plugin architecture within Enterprise Server. |
Rebalancer |
Process that balances replicas across the Xpand nodes. |
Replica |
Slice of a representation written to disk. |
Representation |
Table data as defined by an index. Table with multiple indexes generates multiple representations of its data. |
Slice |
Distribution of rows in a representation. Representations typically multiple slices, which are in turn written to disk as replicas. |
Examples
Creating an Xpand Table
To create a table that uses the Xpand storage engine, use the CREATE TABLE statement with the ENGINE=Xpand option:
CREATE DATABASE hq_sales;
CREATE TABLE hq_sales.invoices (
invoice_id BIGINT UNSIGNED AUTO_INCREMENT NOT NULL,
branch_id INT NOT NULL,
customer_id INT,
invoice_date DATETIME(6),
invoice_total DECIMAL(13, 2),
payment_method ENUM('NONE', 'CASH', 'WIRE_TRANSFER', 'CREDIT_CARD', 'GIFT_CARD'),
PRIMARY KEY(invoice_id)
) ENGINE = Xpand;
SELECT TABLE_SCHEMA, TABLE_NAME, ENGINE
FROM information_schema.TABLES
WHERE TABLE_SCHEMA='hq_sales'
AND TABLE_NAME='invoices';
FAQ
How many nodes should my MariaDB Xpand deployment have?
A MariaDB Xpand deployment should have 3 or more nodes to provide high availability, and it should have an odd number of nodes to avoid a split-brain scenario.