arrow-left

All pages
gitbookPowered by GitBook
1 of 1

Loading...

Understanding MaxScale's Read/Write Split Router

Get an overview of the readwritesplit router. Learn how it splits traffic for MariaDB replication and Galera clusters to enhance scalability and performance.

MaxScale's Read/Write Split Router (readwritesplit) performs query-based load balancing. For each client connected to MaxScale, it opens up connections to multiple back-end database servers. When the client sends a write query to MaxScale, it routes the query to the connection opened with the primary server. When the client sends a read query to MaxScale, it routes the query to a connection opened with one of the replicas.

hashtag
What Does the Read/Write Split Router Support?

The Read/Write Split Router (readwritesplit) supports:

  • deployments.

  • deployments.

  • and deployments.

hashtag
When to Use the Read/Write Split Router?

The allows you to:

  • Perform query-based load balancing.

  • Route client connections to multiple servers simultaneously.

  • Route write queries to primary and read queries to replicas.

This page is: Copyright © 2025 MariaDB. All rights reserved.

Automatically reconnect clients to the new primary after failover or switchover.
  • Automatically replay transactions on the new primary after failover or switchover.

  • Automatically retry failed queries.

  • Enforce causal reads to avoid reading stale data caused by slave lag.

  • MariaDB replicationarrow-up-right
    Galera Clusterarrow-up-right
    Columnstore Object Storagearrow-up-right
    ColumnStore Shared Local Storagearrow-up-right
    Read/Write Split Router (readwritesplit)
    spinner