What is a UUID, and Why Should You Care?

When working with a database, it’s common practice to use some kind of id field to provide a unique identifier for each row in a table. Imagine, for example, a customers table. We wouldn’t want to use fields such as name or address as unique identifiers, for example, because it’s possible more than one customer […]

When working with a database, it’s common practice to use some kind of id field to provide a unique identifier for each row in a table.
Imagine, for example, a customers table. We wouldn’t want to use fields such as name or address as unique identifiers, for example, because it’s possible more than one customer could have the same name, or share the same address.
Instead, it’s a good idea to assign each row some kind of unique identifier.
Source: CockroachDB