MySQL Load Balancers - MaxScale, ProxySQL, HAProxy, MySQL Router & nginx - a close up look
summary
Compares MaxScale, ProxySQL, HAProxy, MySQL Router and nginx with concrete behaviors: MaxScale 2.0 shows CPU contention and 95th-percentile latency spikes (one test hits 25s latency), 2.1 improves but had scalability limits; ProxySQL offers connection multiplexing, SQL-driven configuration, rich query rules and native caching with 1.4 adding Group Replication support; HAProxy and nginx act as TCP proxies and require external health scripts (clustercheck or an iptables-based daemon) to handle Galera/replica states; example claim: 2,000 app connections can be squeezed to ~100 back-end sessions.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:58Why load balancers?
- 6:37Application connectors
- 8:25Reverse proxies - HAProxy
- 10:59Reverse proxies - Keepalived
- 12:27Reverse proxies - NGINX
- 15:06SQL-aware proxies - MaxScale
- 25:48SQL-aware proxies - ProxySQL
- 34:57SQL-aware proxies - MySQL Router
- 41:34Health checks used with proxies - clustercheck-iptables
- 43:36Summary
related talks
37mScale MySQL beyond limits with ProxySQL
08mMySQL as a Layered Service: How to use Proxy SQL to Control Traffic and Scale Out
35mMySQL HA, Recovery and Load Balancing
27mIntroduction to Configuring and Using MariaDB MaxScale: Database Proxy Made Simple
27mDistributed MySQL Architectures: Past, Present and Future
53mMySQL DevOps
24mComparing the High Availability of MySQL with Modern Distributed SQL Databases
55mProxySQL Use Case Scenarios