Dirty Reads, Explained
A dirty read returns an uncommitted value from another transaction. If that transaction rolls back, the reader observed a value that was never part of committed database state.
A dirty read returns an uncommitted value from another transaction. If that transaction rolls back, the reader observed a value that was never part of committed database state.
A transaction reads the same row twice and gets two different committed values. The isolation level determines whether both reads use the same database state.
A transaction repeats a search and finds an additional matching row. The existing rows did not change, but another transaction committed a new row that satisfies the same query.
Deploying code to production is irreversible in the short term - when something goes wrong, rolling back requires another deploy, which takes time and may have its own risks. Feature flag allows you to revert fast
73 practical lessons across 2 courses
Currently covering
Practical deep-dives on software craft, career leverage, and building things that matter.