This article explains how InnoDB's redo log works as a safety cushion, detailing its generation, buffering, flushing, circular storage, and recovery process to ensure transaction durability even when the database crashes unexpectedly.
File systems risk data corruption during power loss or crashes because writes are not atomic, so journaling—recording intended operations in a write‑ahead log before committing them—ensures metadata and user data consistency, with variations like data journaling and ordered (metadata) journaling improving performance and reliability.
Journal file systems use write‑ahead logging to record each write operation as a transaction, ensuring that after power loss or crashes the system can replay logs and maintain metadata and user‑data consistency, avoiding corruption and space waste through techniques like data, ordered, and metadata journaling.
The article explains the differences between cache and buffer, how Oracle’s log buffer and data buffer cache interact with various storage‑level caches, and why write‑back, battery‑backed caches, RAID and disk cache settings are crucial for maintaining data consistency during power loss.
Journal file systems protect against data corruption caused by power loss or crashes by recording each write operation as a transaction in a dedicated log, then committing the changes only after the log is safely stored, enabling replay to restore consistency.
This article explains the ACID properties, write‑ahead logging, and how RocksDB implements a three‑step write path and a leader‑follower Group Commit mechanism to improve transaction throughput by batching fsync operations.
This article introduces SQLite, a lightweight ACID‑compliant relational database widely used in mobile devices, detailing its zero‑configuration design, key features, limitations, transaction and locking mechanisms, and the Write‑Ahead Logging mode that enables concurrent reads and writes.
