Explore >> Select a destination
|
You are here 
|
martin.kleppmann.com | ||
| | | | |
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
|
|
| | | | | My notes from Chapter 7 of 'Designing Data-Intensive Applications' by Martin Kleppmann. | |
| | | | |
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... | |
| | | | |
timilearning.com
|
|
| | | One common pattern in the previous systems we have discussed like MapReduce, GFS, and VMware FT is that they all rely on a single entity to make the key decisions. While this has the advantage of making it easier for the system to decide, the downside of this approach is that the entity is now a single point of failure. In this post, we'll learn how the Raft consensus algorithm solves this problem. | ||
