How transaction isolation is achieved in the databases? What trade-offs should we consider?
Can we let clients to read data, while individual is modifying the same data at the same time?
Transaction isolation levels were defined based on phenomena which are prohibited for different levels. Locking and versioning are utilized to isolate concurrent access to the same data by multiple clients. Each of these approaches will trade off with throughput and consistency. knowing of both approaches will aid you to make decisions erstwhile it comes to scaling your database.
We will play with PostgreSQL to see different phenomena for different transaction isolation level.
We will effort to realize how PostgreSQL implemented transaction isolation. We will look under the hood how the row version is checked. We will see the implications of versioning and how to deal with them (VACUUM)
