Deep Dive into UUID Versions: When to Use v1, v4, or v7
Learn the differences between UUID versions. Discover why UUID v7 is replacing v4 for modern database primary keys and RFC 9562 compliance.
📋 Table des Matières
The Universally Unique Identifier (UUID) is the cornerstone of distributed computing. When you need to generate an ID for a database record, a session, or an API object without checking a central authority, the UUID is your only reliable choice.
However, many developers don't realize that there are multiple versions of UUIDs, each designed for a specific engineering trade-off. Choosing the wrong one can lead to privacy leaks or massive database performance degradation. This guide breaks down the three most relevant versions today: v1, v4, and the new v7 standard.
1. UUID v1: The Time-Based Legacy
The UUID v1 is the "classic" version. It is generated using a combination of the current high-resolution timestamp and the MAC address of the machine (the "Node ID") that generated it.
### The Conflict:
- Advantage: v1 IDs are naturally time-ordered.
- Disadvantage (Privacy): Because the MAC address is embedded in the ID, a v1 UUID leaks exactly which physical server generated the ID and at what exact microsecond. In modern cloud environments with ephemeral containers, this is often considered a security risk.
Karuvigal Team
Building developer tools that save time and improve productivity.