# ACID transactions on object storage

Glossary, read 10 Nov 2026

**The short answer.** ACID means atomicity, consistency, isolation and durability. Object stores such as S3 do not offer multi-file transactions, so table formats supply them: each commit atomically publishes a new metadata version that readers either see completely or not at all. Delta Lake, Iceberg and Hudi each do this differently.

Concurrent writers are managed with optimistic concurrency control: no locks are held, writers check for conflicts at commit and retry or fail.

Transactions across several tables are a separate feature that needs catalog support on some platforms.

## A sourced example

Databricks's page says it provides snapshot isolation on reads and write-serializable isolation on writes by default, and that multi-table transactions require catalog commits enabled on the participating tables.

## Sources

- What are ACID guarantees on Databricks?: https://docs.databricks.com/aws/en/lakehouse/acid (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/glossary/acid-transactions/
