Topologies Overview

MariaDB offers varied deployment topologies by workload and technology, each named and diagrammed with benefits listed. Custom configurations are also supported.

MariaDB products can be deployed in many different topologies. The topologies described in this section are representative of the overall structure. MariaDB products can be deployed to form other topologies, leverage advanced product capabilities, or combine the capabilities of multiple topologies.

Topologies are the arrangements of nodes and links to achieve a purpose. This documentation describes a few of the many topologies that can be deployed using MariaDB database products.

We group topologies by workload (transactional, analytical, or hybrid) and technologies (Enterprise Spider). Single-node topologies are listed separately.

To help you select the correct topology:

• Each topology is named, and this name is used consistently throughout the documentation.

• A thumbnail diagram provides a small-scale summary of the topology's architecture.

• Finally, we provide a list of the benefits of the topology.

Although multiple topologies are listed on this page, the listed topologies are not the only options. MariaDB products are flexible, configurable, and extensible, so it is possible to deploy different topologies that combine the capabilities of multiple topologies listed on this page. The topologies listed on this page are primarily intended to be representative of the most commonly requested use cases.

Transactional (OLTP)

Primary/Replica Topology

MaxScale routes reads to two replicas and writes to one primary, which replicates to both.

MariaDB Replication

• Highly available

• Asynchronous or semi-synchronous replication

• Automatic failover via MaxScale

• Manual provisioning of new nodes from backup

• Scales read via MaxScale.

• Enterprise Server 10.3+, MaxScale 2.5+

Galera Cluster Topology

MaxScale routes to three Galera Cluster nodes that replicate virtually synchronously with each other.

Galera Cluster Topology Multi-Primary Cluster Powered by Galera for Transactional/OLTP Workloads

• InnoDB Storage Engine

• Highly available

• Virtually synchronous, certification-based replication

• Automated provisioning of new nodes (IST/SST)

• Scales reads via MaxScale Enterprise Server 10.3+, MariaDB Enterprise Cluster (powered by Galera), MaxScale 2.5+

Analytical (OLAP, Data Warehousing, DSS)

ColumnStore Shared Local Storage Topology

Diagram	Features
	Columnar storage engine with shared local storage Highly available Automatic failover via MaxScale and CMAPI Scales reads via MaxScale Bulk data import Enterprise Server, ColumnStore, MaxScale Optional Read Replica topology

ColumnStore Object Storage Topology

MaxScale routes to three ColumnStore nodes that all read and write the same S3 object storage.

Columnar storage engine with S3-compatible object storage

• Highly available

• Automatic failover via MaxScale and CMAPI

• Scales reads via MaxScale

• Bulk data import

• Enterprise Server, ColumnStore, MaxScale

Hybrid Workloads

HTAP Topology

MaxScale routes HTAP traffic to one server that replicates from InnoDB to S3-backed ColumnStore.

• Single-stack hybrid transactional/analytical workloads

• ColumnStore for analytics with scalable S3-compatible object storage

• InnoDB for transactions• Cross-engine JOINs

• Enterprise Server, ColumnStore, MaxScale

_{This page is: Copyright © 2026 MariaDB. All rights reserved.}