Strong sync replication can be configured. In the master/slave architecture, strong sync can ensure master/slave data consistency to avoid data loss in case of master/slave switchover. Of course, you can modify the configuration to disable strong sync to improve database performance.
TencentDB for MariaDB is designed to achieve an availability of over 99.99%. It provides master/slave hot backup or two slaves for one master (where the two slaves are used to implement imperceptible failover). In addition, it has features such as automatic recovery of faulty nodes, automatic backup, and rollback to facilitate smoother and securer business operations.
Based on the configuration of your purchased instances, TencentDB for MariaDB usually adopts the architecture of two nodes (one master and one slave) or three nodes (one master and two slaves). Each node is installed on an independent physical machine deployed across racks to ensure that database service will not be affected by network or power failure of a single device or rack.
The physical machine of each TencentDB for MariaDB node adopts the dual-ENI dual-connection switch configuration to ensure security and reliability of the physical network. In actual use, TProxy connects to TGW; when the SET node fails, TProxy can switch database routes within 200 ms at best; if TProxy fails, TGW can schedule the loads to another healthy TProxy within one second; and the switching does not change the access VIP (virtual IP) so as to eliminate the impact caused by change of physical servers.
Backup service: the backup module is responsible for periodically creating (physical) backups and storing binary files (binlogs) of TencentDB for MariaDB. Backup files will be uploaded to a distributed file cluster (HDFS) with a higher level of security. Generally, backup is initiated on slave nodes to avoid impact on services provided by the master node.
Restoration service: it is also known as rollback, where the restoration module restores backup files in HDFS to the temp instance for you to check or adjust without affecting operations of the master instance.
Backup download: you can transfer or download backup files to a specified location, e.g., lower-priced COS.
2-region-3-DC deployment architecture of TencentDB for MariaDB: the straight-line distance between nodes in the same city is greater than 10 KM, and that between nodes in different cities is greater than 100 KM. This architecture can be implemented by Tencent's proprietary high availability (HA) scheduling scheme as shown below:
Based on PCI-E SSD, TencentDB for MariaDB has powerful I/O performance that guarantees the accessibility of database. The storage firmware adopts the NVMe protocol and is specifically designed for PCI-E SSD, bringing TencentDB for MariaDB's superior performance to full play with one single high-IO instance sustaining up to 6 TB storage, 480 GB memory, and at least 220,000 queries per second (QPS). The performance advantage allows you to support higher business concurrence with a smaller number of database instances.
All kernels of TencentDB for MariaDB instances are not native ones but optimized by the TencentDB development team according to actual business needs. In addition, the default parameters are fine-tuned through Tencent Cloud's many years of production practices and continuously improved by professional DBAs, so that TencentDB for MariaDB can always run based on the best practices.
TencentDB for MariaDB uses the InnoDB storage engine and is highly compatible with MySQL 5.5/5.6, which means that code, applications, drivers, and tools that apply to MySQL databases can be directly used in TencentDB for MariaDB with no or only slight change required.