Tag: Distributed transaction consistency

2 Posts

In-depth analysis of database and table sharding: principles, primary key generation, paging query, distributed transactions and high availability practices
1. Introduction In large-scale Internet applications, as the amount of data continues to grow, the single-database, single-table architecture cannot meet the needs of high concurrency and large data storage. Sub-database and sub-table is a common database architecture optimization solution, which can improve database throughput, reduce the amount of data in a single table, and improve query efficiency. However, sub-database and sub-table also bring many complex problems, such as primary key generation, paging query, distributed transaction, cross-table query, high availability, etc. This article will explain in detail the core concepts, key technologies and implementation methods of sub-database and sub-table…
Will data be lost after a database transaction is committed? In-depth analysis of persistence mechanisms and optimization solutions
Introduction In database systems, transaction durability is the most critical part of the ACID feature. It promises that once a transaction is successfully committed, the modified data will take effect permanently, and the data will not be lost even if the system crashes or hardware fails. However, the realization of this promise is not as simple as it seems. Will the data really not be lost after the transaction is committed? This depends on the database's internal log mechanism, persistence strategy, distributed architecture design, and hardware redundancy capabilities. This article will start from a single...