/explore
|
You are here 
|
timilearning.com | ||
| | | | |
johnjr.dev
|
|
| | | | | When we study transactions in relational databases, one of the first things we learn are the guarantees that a transaction must provide. ACID(Atomicity, Consistency, Isolation, Durability) are the properties that we desire. Here, I will discuss the Isolation level in more detail and show that atomicity alone is not enough when handling concurrency. One classic example of the importance of atomicity is moving money between accounts. So, imagine that we have two accounts and we would like to transfer the total amount from one account to another one. In a relational database, what we need to do is three steps: | |
| | | | |
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. | |
| | | | |
blog.dancrisan.com
|
|
| | | | | In real life, users access a database concurrently. Database access is done through transactions. What is a transaction? a unit of work that has to be treated as "a whole" it has to happen in full or not at all A real life example of a transaction... | Dan Crisan | Techie, Blogger, Diversity Advocate and A Little Bit More . This is my technical blog (: | |
| | | | |
timilearning.com
|
|
| | | My notes from the third chapter of Martin Kleppmann's book: Designing Data Intensive Applications. | ||
