Designing for MaxScale's Read/Write Split Router
Contents
Overview
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 route queries?
- How does the Write Split Router reconnect client connections to the new primary server after automatic failover?
- How does the Read/Write Split Router retry failed reads?
Additional information is available here.
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.