Layer 7 capabilities for MySQL traffic
FortiADC provides application-aware load balancing for MySQL database traffic, supporting both traditional replication and advanced distributed database architectures. It intelligently distributes traffic to MySQL servers based on read/write intent, user, SQL type, and more.
Packet Processing
Single-Primary Mode
FortiADC supports processing traffic by the following rules in Single-Primary Mode.
-
Write operations (INSERT, UPDATE, DELETE) go to a designated primary MySQL server.
-
Read operations (SELECT) are offloaded to one or more secondary servers.
-
Default behavior is auto-applied, but can be customized with user-defined rules.
Common use cases of Sharding mode include web applications with high read-to-write ratio, E-commerce platforms with real-time inventory reads and transactional writes, etc.
Sharding Mode
In Sharding mode, different subsets of data are processed by different server groups. FortiADC supports setting the following rules in Sharding mode:
-
Range-based: routes queries by key ranges.
-
Hash-based: uses a hashed key to distribute traffic.
Common use cases of Sharding mode include Large SaaS apps or ERPs needing high concurrency and database scaling, Apps with tenant-based data (multi-group) and heavy transactional loads, etc.
Advanced MySQL-Aware Features
-
Granular rules for routing based on:
-
SQL statements (SELECT, INSERT, etc.)
-
Database, table, user, Client IP
-
-
Multiple user-defined MySQL profiles can be created.
-
Uses a valid MySQL user account to parse and inspect SQL requests.
Content Routing
FortiADC doesn't support content routing for MySQL traffic.
Load Balancing Methods
Round Robin, Least Connection
Persistence
FortiADC doesn't support persistence for MySQL traffic.
Security Check
FortiADC doesn't support security check for MySQL traffic.