An isolation level defines which observations are allowed across concurrent transactions. A lower level can increase concurrency but may allow a repeated read within one transaction to return a different value.
The demo places a T2 commit between two T1 reads and compares the visible result. Exact guarantees differ across database engines, so check the engine documentation.
When to use
Choose an isolation level when concurrent updates or repeated reads affect business rules.