/explore
|
You are here 
|
blog.dancrisan.com | ||
| | | | |
surfingcomplexity.blog
|
|
| | | | | In the previous blog post, we saw how a transaction isolation strategy built on multi-version concurrency control (MVCC) does not implement the serializable isolation level. Instead, it implements a weaker isolation level called snapshot isolation. In this post, I'll discuss how that MVCC model can be extended in order to achieve serializability, based on work... | |
| | | | |
sookocheff.com
|
|
| | | | | Title and Author of Paper Generalized Isolation Level Definitions, Adya et al. Summary The ANSI SQL standard defines isolation levels allowing database users to trade off between performance and consistency when running transactions. Unfortunately, the wording in the SQL standard is geared towards locking as the sole supported concurrency method. This paper presents alternative definitions to the isolation levels specified in the ANSI SQL standard that are general enough to allow for any concurrency method (multi-version, optimistic, etc.) to be used. | |
| | | | |
timilearning.com
|
|
| | | | | Distributed databases typically divide their tables into partitions spread across different servers which get accessed by many clients. In these databases, client transactions often span the different servers, as the transactions may need to read from various partitions. A distributed transaction is a database transaction which spans multiple servers. This post will detail how databases guarantee some ACID properties when executing distributed transactions. | |
| | | | |
databasearchitects.blogspot.com
|
|
| | | A blog by and for database architects. | ||
