Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

TencentDB for MySQL Database Proxy

intl.cloud.tencent.com

  • Free trial
  • Web
  • API

What TencentDB for MySQL Database Proxy is

TencentDB for MySQL Database Proxy is a managed service placed between an application and TencentDB for MySQL. Applications use a separate proxy address, while the proxy routes reads to read-only instances and writes to the source instance through one connection address. Connection pooling can reduce load from frequent or excessive new connections, and transaction splitting can separate reads and writes within a transaction. A multi-node cluster with cross-availability-zone deployment supports failover and availability. Resources are isolated per database instance, and each proxy can process up to 100,000 requests per second. Nodes can scale from 1 to 60, with request, CPU and memory metrics monitored every second. Configuration changes, source switches and read-only instance changes can be hot-loaded without disconnecting or restarting networks. Balanced access spreads connections across proxy nodes, while nearby access selects a node by availability zone or path. Supported databases are MySQL 5.7, MySQL 8.0 and the TencentDB read-only analysis engine.

Who it suits

This proxy suits teams running supported TencentDB for MySQL environments that need routing, pooling, load balancing and failover. It is delivered as a managed web and API service.

Good to know, and what to watch

  • Routes reads and writes through one address
  • Supports connection pooling and transaction splitting
  • Multi-node, cross-zone failover design
  • Scales proxy nodes from 1 to 60
  • Monitors metrics at second-level granularity
  • No free plan
  • Network forwarding disables several proxy features
  • Connection pooling requires specified MySQL kernel versions
  • Paid plan listed at $0.07 a month

Database Proxy (pay-as-you-go)

$0.07/mo

15-day trial

The verdict

TencentDB for MySQL Database Proxy centralizes traffic management and availability features for supported TencentDB deployments. Review the network-forwarding restrictions, version requirements and paid billing details before adopting it.

What the maker publishes

Access modes
Balanced distribution spreads connections across proxy nodes, while nearby access selects a node in the same availability zone or with the shortest path. source
Availability
The proxy uses a multi-node cluster and cross-availability-zone deployment to support failover and availability. source
Connection pooling
Connection pooling can reduce load caused by frequent new connections and excessive connections. source
Hot reload
Proxy configuration can be hot-loaded after source switching, configuration changes, or read-only instance additions and removals without network disconnections or restarts. source
Isolation and performance
Proxy resources are isolated per instance, and each proxy can process up to 100,000 requests per second. source
Network forwarding limits
With network forwarding enabled, adaptive load balancing, connection pooling, and transaction splitting are unsupported. source
Purpose
The proxy sits between TencentDB for MySQL and an application and relays database requests through a separate proxy address. source
Read/write routing
It can route read requests to read-only instances and write requests to the source instance through one application connection address. source
Scaling and monitoring
Proxy nodes can be dynamically scaled from 1 to 60, and performance metrics such as request counts, CPU, and memory are monitored at second-level granularity. source
Transaction splitting
Transaction splitting can send reads and writes within a transaction to different instances to reduce source-instance load. source
Trial offer
The billing announcement describes a 15-day proxy free-trial promotion for up to three instances per Tencent Cloud UIN account, with a specified discounted node capacity. source
Version requirement
Connection pooling requires MySQL 5.7 kernel minor version 20211030 or later, or MySQL 8.0 kernel minor version 20230630 or later. source

Checked against the maker's pages on 8 Oct 2026.