Netflix built a distributed write‑ahead log (WAL) system to guarantee data consistency, durability, and high‑throughput across services, tackling challenges like data loss, cross‑store entropy, multi‑partition updates, replication, and reliable retry for real‑time pipelines.
An in‑depth guide explains MySQL’s write‑ahead log mechanism, covering buffer pool, redo and undo logs, checkpoint types, and how the system recovers from power failures, with step‑by‑step examples and practical configuration tips for reliable data consistency.
This article explains common database logging mechanisms such as MySQL redo logs and binlogs, compares them with Redis AOF and etcd's Raft‑based WAL, and provides an in‑depth analysis of etcd's WAL source code, including key structures, creation process, record types, encoding, and file pipeline management.
This article explains the fundamentals of LSM‑Tree storage engines, introduces SSTable concepts, describes how to build and maintain ordered log files, and provides a complete Java implementation of a tiny key‑value store with code examples and design analysis.
The article explains how Write Ahead Log (WAL) improves metadata persistence and disaster recovery in distributed storage systems such as HDFS by buffering changes, reducing synchronous database writes, and providing checkpoint and recovery mechanisms, while also discussing practical control options.
The article explains HBase’s write‑ahead‑log architecture, detailing how client put/delete requests travel through RPC to the RegionServer, are processed by MultiRowMutationService, written to the WAL via FSHLog.append and sync, and finally stored in MemStore, while describing durability options and the underlying source‑code call chain.
