What do you use UUID for?
UUIDs are generally used for identifying information that needs to be unique within a system or network thereof. Their uniqueness and low probability in being repeated makes them useful for being associative keys in databases and identifiers for physical hardware within an organization.
How do I generate a UUID 1?
Version-1 UUIDs are generated from a time and a node ID (usually the MAC address); version-2 UUIDs are generated from an identifier (usually a group or user ID), time, and a node ID; versions 3 and 5 produce deterministic UUIDs generated by hashing a namespace identifier and name; and version-4 UUIDs are generated …
How are integer values compared to UUID values?
Integer values are compared up to 8 bytes at a time by the CPU but UUID values are compared char per char. Databases are rarely CPU bound, but nevertheless this adds to the latencies of the queries. If you are not convinced, look at this performance comparison between integers vs strings:
Which is better for performance int or UUID?
Of course UUID may take a little more time (and space), but this is not a performance bottleneck for most (if not all) cases. Having a column as Primary Key should make both choices equal wrt to performance.
Why is it good to use a UUID as a PK?
Reasons UUIDs are Good. There are several reasons using a UUID as a PK would be great compared to auto-incrementing integers: At scale, when you have multiple databases containing a segment (shard) of your data, for example a set of customers, using a UUID means that one ID is unique across all databases, not just the one you’re in now.
When to use UUID or INT for primary key?
By using UUID, you can generate the primary key value of the parent table up front and insert rows into both parent and child tables at the same time within a transaction. Besides the advantages, UUID values also come with some disadvantages: