UUID Versions Explained: v1, v3, v4, v5

Overview of UUID Versions

The RFC 4122 specification defines five official UUID versions, each utilizing distinct design architectures to serve different technological objectives. Understanding these variations is essential for software engineering teams selecting the right identifier structure for system scaling.

UUID v1: Time & Node Based

Version 1 UUIDs are generated by combining the host computer's MAC address (node identifier) with a 60-bit timestamp representing 100-nanosecond intervals since October 15, 1582. Because they incorporate time, they are naturally semi-sortable. However, they expose the generating system's MAC address and precise time, posing privacy and security risks in public APIs.

UUID v4: Fully Random

Version 4 UUIDs rely entirely on random or pseudo-random bits. Out of the 128 bits, 122 bits are allocated for randomness (the remaining 6 bits are reserved for variant and version notation). This is the most popular choice for modern web microservices because it ensures high privacy and is easy to generate client-side without system dependencies.

UUID v3 & v5: Namespace & Name Based

Versions 3 and 5 are deterministic namespace-based identifiers. They hash a namespace UUID (like DNS, URL, OID, or X.500) and a user-provided string. The difference lies in the hashing algorithm: Version 3 uses MD5, whereas Version 5 utilizes the more secure SHA-1 algorithm. If you supply the same namespace and name, you will always get the exact same UUID, which is ideal for deduplication.

Next-Gen Specifications: UUID v7

Although not in the original RFC 4122, the updated IETF draft specifies new versions, with UUID v7 gaining significant traction. Version 7 features an epoch-timestamp layout that natively supports sorting and prevents clustered index fragmentation in databases, making it the modern standard for transactional backends.