Explore >> Select a destination
|
You are here 
|
tigerbeetle.com | ||
| | | | |
ducklake.select
|
|
| | | | | DuckLake simplifies lakehouses by using a standard SQL database for all metadata, instead of complex file-based systems, while still storing data in open formats like Parquet. This makes it more reliable, faster, and easier to manage. | |
| | | | |
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: | |
| | | | |
buttondown.com
|
|
| | | | | One thing about concurrency control ("isolation") in a transactional database is that it incurs costs, and there's broadly two kinds of such costs. The first... | |
| | | | |
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. | ||
