Deployment Targets

The final step in deploying MariaDB Enterprise is to install, configure, start, and test.

MariaDB Enterprise can be deployed in several possible topologies and configurations to meet business needs to serve transactional, analytical, and hybrid workloads.

This guide provides step-by-step instructions for preparing a system to serve in the following roles:

Deployment Target

Description

Single Standalone MariaDB Enterprise Server

Non-production database server for testing and development

Single Standalone MariaDB Community Server

Non-production database server for testing and development

Primary/Replica Topology with MariaDB Enterprise Server

Primary and Replica servers for asynchronous and semi-synchronous replication

Primary MariaDB Community Server

Primary (master) for asynchronous and semi-synchronous replication

Replica MariaDB Community Server

Replica (slave) for asynchronous and semi-synchronous replication

MariaDB Enterprise Cluster Node

Node participating in virtually synchronous clustering using Galera Cluster

MariaDB Galera Cluster Node

Node participating in virtually synchronous clustering using Galera Cluster

MariaDB Enterprise Spider Node

Node that fetches data from federated database servers

MariaDB Community Spider Node

Node that fetches data from federated database servers

Single-Node Enterprise ColumnStore Server

Single MariaDB Enterprise Server with MariaDB Enterprise ColumnStore

Single-Node ColumnStore Server

Single MariaDB Community Server with MariaDB ColumnStore

Multi-Node Enterprise ColumnStore Cluster

Multiple MariaDB Enterprise Servers with MariaDB Enterprise ColumnStore

HTAP Deployment (MariaDB Enterprise Server)

Hybrid Transactional-Analytical Processing

HTAP Deployment (MariaDB Community Server)

Hybrid Transactional-Analytical Processing

MaxScale with MariaDB Replication using Read/Write Split Router

Monitoring for MariaDB Replication with automatic failover and automatic rejoin, load balancing by read/write splitting, traffic routing, database proxy

MaxScale with MariaDB Replication using Read Connection Router

Monitoring for MariaDB Replication with automatic failover and automatic rejoin, load balancing by connection, traffic routing, database proxy

MaxScale with MariaDB Enterprise Cluster using Read/Write Split Router

Monitoring for MariaDB Enterprise Cluster, load balancing by read/write splitting, traffic routing, database proxy

MaxScale with MariaDB Enterprise Cluster using Read Connection Router

Monitoring for MariaDB Enterprise Cluster, load balancing by read/write splitting, traffic routing, database proxy

This guide provides step-by-step instructions for upgrading the following products:

Product

Description

Upgrade from MariaDB Community Server to MariaDB Enterprise Server

Including single standalone server, primary, and replica configurations

Upgrade MariaDB Enterprise Server to a Newer Major Release

Including single standalone server, primary, and replica configurations

Upgrade MariaDB Community Server to a Newer Major Release

Including single standalone server, primary, and replica configurations

Upgrade MariaDB Enterprise Server to a Newer Minor Release

Including single standalone server, primary, and replica configurations

Upgrade MariaDB Community Server to a Newer Minor Release

Including single standalone server, primary, and replica configurations

Upgrade a Single-Node MariaDB Enterprise ColumnStore Server from 1.2

For single-node Enterprise ColumnStore upgrades from 1.2

Upgrade a Single-Node MariaDB ColumnStore Server from 1.2

For single-node ColumnStore upgrades from 1.2

Upgrade a Multi-Node MariaDB Enterprise ColumnStore Cluster from 1.2

For multi-node Enterprise ColumnStore upgrades from 1.2

MariaDB MaxScale

Including MaxScale instance configuration