Posts

Showing posts with the label dirty read

Lock in Database

Image
Introduction In the database world, a lock is a mechanism that helps the system manage simultaneous access and modification of data by multiple users or processes at a single point in time. This is the exact solution to ensure privacy and safety, because allowing unrestricted, uncontrolled access and modification of data will cause everything to become chaotic. Locks are not created to slow down the system, but rather a mandatory blocking mechanism to keep data accurate and consistent when thousands of users access it simultaneously. Why Do We Need Locks Without locks, the system will fall into a data conflict state leading to data corruption, which can cause three classic problems: Lost Update: Two users modify the same row of data at the same time and the user who saves later will overwrite and completely lose the data of the previous user. Dirty Read: You read data that is being modified by someone else, but they have not committed yet. If they perform a rollback afterwards, the dat...