Designing for MaxScale's Read/Write Split Router
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Read/Write Split Router
Topics on this page:
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.
This page contains topics that need to be considered when designing applications that use the Read/Write Split Router.
How does the Read/Write Split Router select replica servers to load balance queries?
How does the Read/Write Split Router ensure that load-balanced read-only queries are causally consistent?
How does the Read/Write Split Router reconnect client connections to the new primary server after automatic failover?
How does the Read/Write Split Router retry failed queries during automatic failover?
Additional information is available in the MariaDB Knowledge Base.