tencent cloud

TDSQL Boundless

Release Notes
Product Introduction
Overview
Scenarios
Product Architecture
Instance Types
Compatibility Notes
Kernel Features
Kernel Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Billing
Billing Overview
Purchase Method
Pricing Details
Renewal
Overdue Payments
Refund
Getting Started
Creating an Instance
Connect to Instances
User Guide
Data Migration
Data Subscription
Instance Management
Configuration Change
Parameter Configuration
Account Management
Security Group
Backup and Restoration
Database Auditing
Tag Management
Use Cases
Technical Evolution and Usage Practices of Online DDL
Lock Mechanism Analysis and Troubleshooting Practices
Data Intelligent Scheduling and Related Practices for Performance Optimization
TDSQL Boundless Selection Guide and Practical Tutorial
Developer Guide
Developer Guide (MySQL Compatibility Mode)
Developer Guide (HBase Compatibility Mode)
Performance Tuning
Performance Tuning Overview
SQL Tuning
DDL Tuning
Performance White Paper
Performance Overview
TPC-C Test
Sysbench Test
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Security Group APIs
Task APIs
Backup APIs
Rollback APIs
Parameter APIs
Database APIs
Data Types
Error Codes
General Reference
System Architecture
SQL Reference
Database Parameter Description
TPC-H benchmark data model reference
Error Code Information
Security and Compliance
FAQs
Agreements
Service Level Agreement
Terms of Service
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-06 18:48:24

Overview

Distributed database transactions refer to a set of database operations executed across multiple nodes or shards within a distributed database system. These operations are either fully executed or not executed at all to maintain a consistent state of the database.

The Basic Properties of Transactions (ACID)

Distributed database transactions adhere to the ACID principles:
Atomicity: All operations in a transaction are either fully completed or not executed at all. TDSQL Boundless uses the two-phase commit protocol (2PC) to ensure the atomicity of transactions.
Consistency: Before and after transaction execution, the database transitions from one consistent state to another consistent state.
Isolation: Concurrently executed transactions are isolated from each other. TDSQL Boundless supports Read Committed and Repeatable Read isolation levels.
Durability: Once a transaction is committed, its results are permanently saved in the database. TDSQL Boundless synchronizes data to multiple replicas via the Raft protocol, ensuring that transaction data will not be lost as long as a majority of replicas survive.


도움말 및 지원

문제 해결에 도움이 되었나요?

피드백