LukeParke/unicorn-utterances
1
0
Fork 0
mirror of https://github.com/LukeHagar/unicorn-utterances.git synced 2025-12-09 21:07:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed a few things in the UUIDv2 article

Browse Source
This commit is contained in:
qarnax801
2023-01-15 22:37:37 +01:00
parent 7d1d6c2695
commit 25e6c22a3e
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
content/blog/what-happened-to-uuid-v2/index.md
View File

@@ -18,13 +18,13 @@ If you read [my last post introducing UUIDs](/posts/what-are-uuids), you'll reme
After this, [I left a very short (one or two sentences) explanation of what a UUIDv2 is](/posts/what-are-uuids#UUIDv2).
Why would I do that [when UUIDv3 and UUIDv5 got four whole headers worth of explanation](/posts/what-are-uuids#UUIDv3and5)? What makes UUIDv2 different or "weird," as I put it?
Why am I dedicating another article to UUIDv2? What makes it different or "weird?
The answer is that while UUID _is_ a form of UUID by some definitions, it effectively is not in others.
> What?!
I know... It's a bit jarring. What's worse, even within the definitions we _do_ have, UUID is deeply flawed. Enough so that most are comfortable leaving it in the past.
I know... It's a bit jarring. But, even within the definitions we have, UUIDv2 is deeply flawed, enough so that most are comfortable leaving it in the past.
To figure out how UUIDv2 became this way, let's explore the following:
@@ -57,7 +57,7 @@ This older specification, which outlined the rules for UUIDv2 and was released i
While the DCE specification is happy to go in-depth about [the fine-grained details of UUIDv2](https://pubs.opengroup.org/onlinepubs/9696989899/chap5.htm#tagcjh_08_02_01_01), let's take a more zoomed-out look at it:
UUIDv2 is almost to [UUIDv1](/posts/what-are-uuids#UUIDv1). It contains most of the same components:
UUIDv2 is almost identical to [UUIDv1](/posts/what-are-uuids#UUIDv1). It contains most of the same components:
- A timestamp
- A version
@@ -112,7 +112,7 @@ UUIDv2 has a lot of problems today:
Both of these feel a bit more like symptoms of a deeper-rooted problem. Dig deep enough, and you'll end up finding what this problem is: **UUIDv2 has a very high likelihood of ID collision**.
This means that if you run UUIDv2 multiple times in rapid succession, the likelihood you'll get the exact same ID.
This means that if you run UUIDv2 multiple times in rapid succession, you're very likely to get the exact same ID.
This is an absolute showstopper for most applications, as the entire idea behind UUIDv1 (which, remember, UUIDv2 is based on) is to generate unique IDs for each generation.
@@ -160,7 +160,7 @@ Well, this is a timestamp. Namely, this is the number of 100 nanoseconds interva
> This date may seem arbitrary, but this is the date of Gregorian reform to the Christian calendar.
Let's use [`dayjs`](https://day.js.org) to see what this equates to in
Let's use [`dayjs`](https://day.js.org) to see what this equates to:
```javascript
// Convert timestamp to milliseconds and add it to the start date