TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
Access Mode
Last updated: 2024-08-29 14:08:08
The access mode is mainly used to control the connection path between an application or the client and the database proxy, which includes Balanced Distribution and Nearby Access. Here, we introduce rules, advantages, and disadvantages of these two access modes above for the database proxy of TencentDB for MySQL.
Prerequisites
You have enabled the database proxy.
The two-node and cluster edition database architecture is required.
Balanced Distribution
Rule: In the Balanced Distribution access mode, the client application connects to all available database proxy nodes. If the database proxy nodes are spread across multiple availability zones, application connections to the database are evenly distributed among all availability zone nodes.
Advantage: Traffic is evenly distributed, resolving the issue of excessive load on a single node.
Disadvantages: If there are proxy nodes in different availability zones, high request latency is prone to occur due to extended access paths.
Nearby Access
Rule: In the Nearby Access mode, the application will connect to the proxy node in the same availability zone or the one with the shortest access path. Even if the database proxy nodes are spread across multiple availability zones, the application will still connect the proxy node with the shortest access path.
Advantage: Low access latency and high speed.
Disadvantage: If your client application changes to an availability zone with fewer database proxy nodes than the original zone, it can lead to excessive load on the nodes and performance delays.
Changing Access Mode
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No