File tree Expand file tree Collapse file tree 1 file changed +6
-3
lines changed
content/crutchcorn/posts/uuid-v6-8 Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change @@ -82,8 +82,11 @@ See, Epoch time is broadly used in nearly every computer system that needs to ke
8282
8383# Make your own UUID rules with UUIDv8 {#UUIDv8}
8484
85- https://blog.devgenius.io/analyzing- new-unique-identifier- formats-uuidv6-uuidv7-and-uuidv8-d6cc5cd7391a
85+ Now comes the fun one of the bunch of new UUID formats: UUIDv8.
8686
87- https://ietf-wg-uuidrev.github.io/rfc4122bis/draft-00/draft-ietf-uuidrev-rfc4122bis.html#name-uuid-version-8
87+ ![ // TODO: Write ] ( ./UUIDv8.svg )
8888
89- ![ // TODO: Write] ( ./UUIDv8.svg )
89+ You'll notice that outside of the encoded variant and version that UUIDv8 allows you to encode any data you'd like.
90+
91+ This is mostly useful for future-proofing UUIDs for the foreseeable future. By allowing whatever format you want as a formalized UUID standard,
92+ vendors (like APIs, databases, and more) can make their own flavors of UUIDs that extend the v8 format for their own needs.
You can’t perform that action at this time.
0 commit comments