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.
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?
A must know topic if you want to understand how databases work, and very well written! thanks Raul.
Neo, Thanks! Appreciate that.
This concept really is foundational.
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.
Very helpful content. Thanks a lot.
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.
very insightful read
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?