High Availability (HA) of MySQL (added in v6.2.0)
We recommend you to use high-availability proxies for front-end multiple MySQL instances. The following table summarizes features of proxies or proxy-like features on popular clouds.
| Proxy features | AWS RDS Proxy | GCP Cloud SQL Auth Proxy | Azure Gateway for MySQL |
|---|---|---|---|
| Primary function | Connection Pooling and Secure Access | Secure IAM Authentication and Encryption | High Availability and Connection Routing |
| Server-side Pooling Support (✅ or ❌)? | ✅ It is used to manage and reuse database connections (multiplexing). | ❌ It is not a connection pooler. It provides a secure tunnel that works with client-side pools. | ❌ It manages connections for HA but does not pool them for reuse across application sessions. |
| IAM/Cloud Auth Support (✅ or ❌)? | ✅ It allows passwordless access using IAM roles. | ✅ This is its core function, enabling secure access via IAM. | ✅ Supports authentication using Azure Active Directory (Entra ID). |
| Automatic Failover (✅ or ❌)? | ✅ It transparently handles failover to a replica, reducing application downtime. | ✅ It is aware of the primary instance and will connect to the newly promoted one. | ✅ This is its primary role. It redirects traffic to the new primary after failover. |
| Multi-Instance Support (✅ or ❌)? | ❌ RDS Proxy is tied to a single RDS database instance or Aurora cluster. | ✅ A single proxy process can be configured to connect to many independent Cloud SQL instances. | ❌ The gateway is part of a single Azure for MySQL server and its associated replicas. |
| Key Restriction | Introduces a small amount of latency and has an additional cost. | Requires a client-side process (e.g., sidecar) and does not reduce the need for client-side pooling. | It is not a configurable, standalone proxy but an integrated feature focused solely on HA for a single server. |
MySQL High Availability (HA) Deployment On-premise
MySQL Router can be used for high-availability on-premises deployment. It can be deployed on the same Kubernetes (K8s) cloud as Boomi Cloud API Management - Local Edition. You can also choose to deploy it in the same or a different namespace. When deploying on the same K8s cluster, ensure you provide labels and annotations to enable routing calls from Boomi Cloud API Management - Local Edition clients to the MySQL Router service.
Refer to Creating HA using MySQL Router - Example deployment for more information.
