7 Comments
User's avatar
Neo Kim's avatar

A must know topic if you want to understand how databases work, and very well written! thanks Raul.

Expand full comment
Raul Junco's avatar

Neo, Thanks! Appreciate that.

This concept really is foundational.

Expand full comment
Saurabh Dashora's avatar

Great explanation, Raul.

WAL is one of those things that we are just used to having without actively thinking about it. But it's a super-critical component of the database.

Expand full comment
ABOUBACAR's avatar

Very helpful content. Thanks a lot.

Expand full comment
Levi Ramsey's avatar

Ultimately, thanks to the WAL, your database is a CQRS/ES system, albeit one that has to make a lot of deoptimizations that aren't necessary when the whole system is designed for CQRS/ES.

Expand full comment
Uriel Bitton's avatar

very insightful read

Expand full comment
Kiruban Kamaraj's avatar

If the committed changes are not immediately written to the main database file from WAL, is there any chance of reading stale data? How does the database prevent this?

Expand full comment