Explore >> Select a destination
|
You are here 
|
fauna.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: | |
| | | | |
christophermeiklejohn.com
|
|
| | | | | ||
| | | | |
timilearning.com
|
|
| | | | | Spanner is a rare example of a distributed database that supports externally consistent distributed transactions. Many other databases either choose not to implement distributed transactions at all, or opt for weaker consistency models because of the performance cost involved. In this post, we'll learn how Google's TrueTime API enables it to provide this guarantee at a good performance. | |
| | | | |
jepsen.io
|
|
| | | |||
