Multi-Node Comparison Tables

MariaDB Enterprise Server supports multi-node implementations to provide high availability, load balancing, and scalability for transactional, analytical, and hybrid use cases. high availability, load balancing, and/or scalability.

Transactional Replication Technologies Comparison

Multi-Node Implementation

High Availability

Data Protection

Scaling

Node Onboarding

Availability

Asynchronous MariaDB Replication

Yes

No

Read

Manual

ES 10.2+

Semi-Synchronous MariaDB Replication

Yes

Yes

Read

Manual

ES 10.2+

Galera Cluster

Yes

Yes

Read

Automatic

ES 10.2+

Distributed SQL with MariaDB Xpand

Yes

Yes with Rebalancing

Read and Write

Automatic

ES 10.5+

Special Purpose Technologies Comparison

Multi-Node Implementation

Use Case

Availability

MaxScale

Database Proxy with Automatic Failover, Read-Write Splitting, Query Routing, Binlog Server, SQL Firewall

ES 10.2+

Multi-Node Enterprise ColumnStore

Analytics with High Availability

ES 10.4+

S3

Archive Read-only Tables in the Cloud

ES 10.3+

Spider

Sharding Tables, Interlinking Databases

ES 10.3+

Delayed MariaDB Replication

Configuring Replica Servers that lag behind the Primary Server

ES 10.2+

Technology Compatibility

Technology

MariaDB Replication

Galera Cluster

Multi-Node Enterprise ColumnStore

MariaDB Xpand

S3

Spider

Included with MariaDB Enterprise Server

Yes

Yes

Yes

Yes

Yes

Yes

Included with MariaDB Community Server

Yes

Yes

No

No

Yes

Yes

MaxScale Monitor

MariaDB Monitor (mariadbmon)

Galera Monitor (galeramon)

MariaDB Monitor (mariadbmon)

Clustrix Monitor (clustrixmon)

N/A

N/A

Supported for InnoDB tables

Yes

Yes

No

No

No

Yes

Supported for ColumnStore tables

Yes

No

Yes

No

No

Yes

Supported for MariaDB Xpand tables

No

No

No

Yes

No

Yes

FAQ

How can MaxScale enhance my multi-node deployment?

MariaDB MaxScale allows applications and clients to connect to a multi-node deployment as they would to a single database server, while abstracting the complexity of the underlying database infrastructure. Key architectural solutions supported by MaxScale include:

Should I use an HTAP deployment for my analytics, or should I use a purely ColumnStore deployment?

MariaDB's Hybrid Transactional-Analytical Processing (HTAP) deployments combine the power of ColumnStore's columnar storage engine with the power of MariaDB's row-based engines, such as InnoDB and MyRocks.

An HTAP deployment is suitable for cases where the following criteria is met:

  • Big data is regularly bulk loaded into tables that use ColumnStore.

  • Transactional data is frequently inserted into, updated in, or deleted from tables that use InnoDB or MyRocks, which function as a system of record.

  • Your applications or reporting systems need to query both the analytical and transactional data.

How many nodes should my multi-node deployment have?

There are many factors involved that can affect the optimal number of nodes in a deployment.

Guidance on the number of nodes required is available for the following topologies:

The best option is to discuss your specific requirements with MariaDB's Enterprise Architects (EAs). Please contact support to find out more information about MariaDB's EA services.