#ProxySQL Use Case Scenarios
summary
ProxySQL sits between apps and MySQL and actually reduces connection overhead (examples claim ratios like 100,000 app connections to 100 DB connections via connection multiplexing), performs dynamic read/write split, enforces query caching with millisecond TTLs (example TTL: 3000 ms), rewrites or blocks bad SQL on the fly, mirrors traffic for testing, and handles failover without dropping app connections by detecting read_only changes. Deployments include multi‑DC SSL setups where local proxies keep remote SSL connections warm to avoid repeated handshakes.
AI-written summary · about
chapters (14)
- 0:00Start
- 20:12Connection Pooling
- 21:36Connection Multiplexing
- 29:00Seamless failover
- 32:13DC migration
- 34:20Improve Multi DC implementation
- 37:01Adoption to Clustering
- 38:23Caching
- 40:51Query Timeout
- 42:21Firewall
- 44:33Query rewrite engine
- 46:10Query retry
- 47:08Query routing
- 47:19Query mirroring
related talks
55mProxySQL Use Case Scenarios
08mMySQL as a Layered Service: How to use Proxy SQL to Control Traffic and Scale Out
37mScale MySQL beyond limits with ProxySQL
27mThe State of ProxySQL, 2020 Edition
41mProxySQL 2021 Dev Submit
06mRoad to Percona Live 2022 - Oleksandr Kuzminskyi - ProxySQL Talk
54mProxySQL at Scale
58mDecentralized Cluster Nodes