# KV Entry Multi-Versioning (MVCC) - Cont'd

__*MVCC*__

![`smart`](./student-guide/diagram/TiKVRegionStorageMVCCAfterChange_aa_001_20221005.png)

+ For example, suppose that `KV` entry `p1` is in `Region 1`:

-------------------------------------------------------------
- By distributing and replicating data by region, TiKV has become a distributed KeyValue system with a certain disaster recovery capability. There is no need to worry about data loss or data loss due to disk failure.
- TiKV supports multi-version consistency control. Imagine a scenario where two clients update the Value of a Key at the same time. If there is no multi-versioning of the data, the data needs to be locked. In a distributed scenario, it may cause performance and deadlock problems. The MVCC implementation of TiKV is implemented by adding the version number after the Key.