Vignesh Prabhu presents a detailed overview of MySQL Router, focusing on its functionalities related to read/write splitting and routing strategies for database management. The presentation covers case studies demonstrating both static and dynamic routing scenarios for InnoDB clusters and replica sets, highlighting configurations, advantages, and limitations. It also includes a comparison of MySQL Router with other load balancers like ProxySQL and MaxScale.

1. Vignesh Prabhu S
Database Expert, Mydbops LLP
Mydbops Open Source Database Meetup - 16th Edition
Scale Your Database Traffic with
Read/Write Splitting using MySQL Router

2. About Me
Vignesh Prabhu S
❏ MySQL Database Expert
❏ 6+ years of IT experience
❏ MySQL Certified DBA
❏ Certified AWS Cloud Architect
❏ Experience in MySQL migrations, upgrades, and
Architecture changes

3. Consulting
Services
Consulting
Services
Managed
Services
● Database Management and
consultancy provider
● Founded in 2016
● Assisted 800+ happy customers
● AWS partners
● PCI & ISO certified
About Us

4. ● Introduction to MySQL Router
● Why MySQL Router? & It’s Features
● MySQL Router: Destination & Routing Strategy
● Evolution of MySQL Router with use cases
● Case 1: Static RW Routing for Standalone Servers
● Case 2: Dynamic RW Split for InnoDB Cluster
● Case 3: Dynamic RW Split for Innodb Replica Set
● Load Balancer Comparison
Agenda

5. Introduction to
MySQL Router

6. ● Part of InnoDB Cluster
● Transparent routing between application and back-end MySQL Servers
● High Availability Solution
● Easily Scalable
Introduction to MySQL Router

7. ● Auto Failover
● Highly Available
● Zero Config Changes during addition / deletion of nodes
Why MySQL Router?

8. ● Transparent Routing - Default
● High Availability - InnoDB Cluster
● Load Balancing
● Routing Strategy - 8.0.4
● Read/Write Splitting - 8.3
● Automatic Failover
● Bootstrap Configuration - Cluster and Replica Set
● Cross-Version Compatibility
Features

9. Destination:-
destinations = 172.31.7.114:3307, 172.31.15.222:3307, 172.31.11.242:3307
Routing Strategy:-
● first-available
● next-available
● round-robin
● round-robin-with-fallback
MySQL Router: Destination & Routing Strategy

10. MySQL Router: first-available

11. MySQL Router: next-available

12. MySQL Router: round-robin

13. MySQL Router: round-robin-with-fallback

14. Evolution of MySQL
Router with use cases

15. Case 1: Static Read and Write
Routing for Master Repl Servers

16. Environment:-
Case 1: Static Read and Write Routing
Nodes IP
Master 1 172.31.13.0:3307
Master 2 172.31.0.131:3307
Replica 1 172.31.7.114:3307
Replica 2 172.31.15.222:3307
Replica 3 172.31.11.242:3307

17. Case 1: Static Read and Write Routing

18. Router Config File:-
[routing:read_only]
bind_address = localhost
bind_port = 6000
destinations = 172.31.7.114:3307, 172.31.15.222:3307, 172.31.11.242:3307
routing_strategy=round-robin
[routing:read_write]
bind_address = localhost
bind_port = 7000
destinations = 172.31.13.0:3307, 172.31.0.131:3307
routing_strategy = next-available
Case 1: Static Read and Write Routing

19. Case 1: Static Read and Write Routing
Advantages:-
● Routing can be done based on the Routing_strategy
● Read and Write Split is available for the static destinations
Limitations:-
● Configuration is Manual
● Automatic Failover is not available
● Dynamic Destinations can’t be added. It requires the restart of the
router.
● Separate Ports needs to be used for Read and Write.

20. Case 2: Dynamic Read and
Write Split for InnoDB Cluster

21. Case 2: Router R/W Split for InnoDB Cluster

22. Cluster Node IPs -
Steps to Configure -
● mkdir -p /home/mydbops/mysql_router
● mysqlrouter -B ibcluster@172.31.13.0:3306 -d /home/mydbops/mysql_router -u
root
Case 2: Router R/W Split for InnoDB Cluster - Configuration
Cluster Nodes IP Hostname
Node 1 172.31.13.0 ip-172-31-13-0
Node 2 172.31.0.131 ip-172-31-0-131
Node 3 172.31.7.114 ip-172-31-7-114

23. Directories & Files Created:-
Case 2: Router R/W Split for InnoDB Cluster - Configuration
File / Directory Purpose
start.sh To start the MySQL Router for the Innodb Cluster
stop.sh To stop the MySQL Router for the Innodb Cluster
mysqlrouter.conf MySQL Router Configuration file for Innodb Cluster
data/state.json Contains Innodb Cluster Primary Information
log/ Log Directory that holds the MySQL router log

24. Router Config File:-
[routing:bootstrap_rw]
bind_address=0.0.0.0
bind_port=6446
destinations=metadata-cache://innodb_cluster/?role=PRIMARY
routing_strategy=first-available
protocol=classic
[routing:bootstrap_ro]
bind_address=0.0.0.0
bind_port=6447
destinations=metadata-cache://innodb_cluster/?role=SECONDARY
routing_strategy=round-robin-with-fallback
protocol=classic
Case 2: Router R/W Split for InnoDB Cluster - Configuration

25. Router Config File:-
[routing:bootstrap_rw_split]
bind_address=0.0.0.0
bind_port=6450
destinations=metadata-cache://innodb_cluster/?role=PRIMARY_AND_SECONDARY
routing_strategy=round-robin
protocol=classic
connection_sharing=1
client_ssl_mode=PREFERRED
server_ssl_mode=PREFERRED
access_mode=auto
Case 2: Router R/W Split for InnoDB Cluster - Configuration

26. Conditions for RW Split:-
● Connection Sharing must be enabled
● Destinations Should be targeted to metadata-cache
● access mode should be in AUTO
● Protocol should be in CLASSIC
● Server & Client ssl modes should be in PREFERRED
Case 2: Router R/W Split for InnoDB Cluster - Configuration

27. Advantages:-
● Bootstrapping is available.
● Automatic Failover for HA system
● Destinations will be changed with respect to the Cluster Node Availability
● Native Support for R/W Split
Case 2: Router R/W Split for InnoDB Cluster

28. Case 3: Dynamic Read and Write
Split for InnoDB Replica Set

29. Case 3: Router R/W Split for InnoDB Replica Set

30. Replica Set Node IPs -
Case 3: Router R/W Split for InnoDB Replica Set
Cluster Nodes IP Hostname
Source 172.31.15.222 ip-172-31-15-222
Replica 172.31.11.242 ip-172-31-11-242

31. Case 3: Router R/W Split for InnoDB Replica Set

32. Router Config File:-
mysqlrouter -B mydbops@ip-172-31-7-51 -d /home/mydbops/router_replicaset -u root
[[routing:bootstrap_rw]
bind_address=0.0.0.0
bind_port=6446
destinations=metadata-cache://innodb_replica_set/?role=PRIMARY
routing_strategy=first-available
protocol=classic
[routing:bootstrap_ro]
bind_address=0.0.0.0
bind_port=6447
destinations=metadata-cache://innodb_replica_set/?role=SECONDARY
routing_strategy=round-robin-with-fallback
protocol=classic
Case 3: Router R/W Split for InnoDB Replica Set

33. Router Config File:-
[routing:bootstrap_rw_split]
bind_address=0.0.0.0
bind_port=6450
destinations=metadata-cache://innodb_replica_set/?role=PRIMARY_AND_SECONDARY
routing_strategy=round-robin
protocol=classic
connection_sharing=1
client_ssl_mode=PREFERRED
server_ssl_mode=PREFERRED
access_mode=auto
Case 3: Router R/W Split for InnoDB Replica Set

34. Advantages:-
● Bootstrapping is available.
● Destinations will be changed with respect to the Cluster Node Availability
● Native Support for R/W Split
Limitation:-
● Manual Failover is required via MySQL admin api
Case 3: Router R/W Split for InnoDB Replica Set

35. Demo:
Router with Innodb Cluster

36. Load Balancer Comparison

37. Load Balancer Comparison
Features MySQL Router ProxySQL Maxscale
Easy Setup with bootstrap function YES Yes NO
Auto Addition of Cluster Nodes YES Yes NO
InnoDB Replica Set support YES NO NO
Auto Addition of Replica Set Nodes YES NO NO
Load Balancing based on Connection YES YES YES
Load Balancing Based on weight NO YES YES
Regex Based routing NO YES YES
Query Caching NO YES YES

38. Thank you!