Video content on UUID design spans conference keynotes, database deep-dives, and short tutorial walkthroughs. This index curates the most educational publicly available videos — each entry includes what the video covers, who it is for, and what you will know after watching.
How this list is organised
Videos are grouped by topic: fundamentals first, then database-specific deep-dives, then language implementation walkthroughs. Each entry notes the approximate runtime and skill level so you can pick the right starting point.
All videos listed are freely available on YouTube. Links open in a new tab.
All video walkthroughs
- Beginner
UUID v7 Explained
Structure, Sorting, and Use Cases
What the timestamp prefix is, why UUID v7 sorts chronologically as a plain string, how the monotonic counter works within a millisecond, and when to pick v7 over v4.
- RFC 9562
- Bit layout
- B-tree indexes
- v4 vs v7
- Intermediate
UUID as Database Primary Keys
Performance Deep Dive
B-tree page fragmentation from UUID v4, how UUID v7 eliminates page splits, storage format benchmarks (BINARY vs VARCHAR), and zero-downtime migration from v4.
- PostgreSQL
- MySQL
- B-tree index
- BINARY(16)
- Migration
- Beginner
RFC 9562 — The Modern UUID Standard
What Changed from RFC 4122
New versions v6, v7, and v8, the Max UUID sentinel, deprecation of v1 and v2, and why the IETF updated the UUID standard after 19 years.
- RFC 9562
- UUID v6
- UUID v7
- UUID v8
- Max UUID
- Beginner
UUID in JavaScript
Tutorial Walkthrough
crypto.randomUUID() vs uuid npm, React hydration errors and how to avoid them, TypeScript branded types for compile-time ID safety, and Prisma/Drizzle ORM setup.
- JavaScript
- React
- TypeScript
- Prisma
- Drizzle
- Beginner
UUID in Python
Tutorial Walkthrough
Standard library uuid module, uuid.uuid7() in Python 3.13, uuid6 backport for earlier versions, Django UUIDField, SQLAlchemy 2.x integration, and FastAPI Pydantic patterns.
- Python 3.13
- Django
- SQLAlchemy
- FastAPI
- Pydantic
- Intermediate
UUID Security
Tokens, Secrets, and What v7 Leaks
The identifier vs secret distinction, what the UUID v7 timestamp discloses, why UUID v4 is not a session token, idempotency key design, and when to use a dedicated secret.
- Security
- Idempotency
- Tokens
- v7 timestamp
- Entropy
- Beginner
UUID in PostgreSQL
Tutorial Walkthrough
Native uuid column type, gen_random_uuid() and uuidv7() functions, PostgreSQL 18 column defaults, pg_uuidv7 extension for PG 14–17, and time-range queries using the UUID index.
- PostgreSQL
- uuidv7()
- pg_uuidv7
- Column defaults
- Index
- Advanced
UUID in Distributed Systems
Video Walkthrough
Event ordering without a central counter, Saga pattern correlation IDs, event sourcing with UUID v7 event IDs, clock skew handling, and UUID v7 vs Snowflake ID comparison.
- Microservices
- Event sourcing
- Saga
- Clock skew
- Kafka
- Intermediate
UUID vs Other ID Formats
ULID, NanoID, and Snowflake
Side-by-side comparison of UUID v7, ULID, NanoID, Snowflake, and KSUID — encoding, length, sortability, RFC status, database native type support, and decision guide.
- ULID
- NanoID
- Snowflake
- KSUID
- Comparison
- Intermediate
UUID v7 ORM Setup
Prisma, Drizzle, Hibernate, SQLAlchemy
App-layer vs database-layer generation, Prisma schema defaults, Drizzle migration, Hibernate @UuidGenerator, SQLAlchemy server_default, and Entity Framework Core configuration.
- Prisma
- Drizzle
- Hibernate
- SQLAlchemy
- EF Core
Frequently asked questions
What is the best way to learn how UUID v7 works?
Start with the bit layout: UUID v7 puts a 48-bit Unix millisecond timestamp in the leading bits, followed by a 4-bit version (7), a 12-bit monotonic counter, the 2-bit variant, and 62 random bits. The timestamp at the front is why v7 sorts chronologically as a plain string — key to B-tree performance. See the UUID Byte Layout guide and the UUID v7 Explained walkthrough.
Do videos on UUID database performance actually explain B-tree fragmentation?
Good UUID database performance videos explain that UUID v4 causes B-tree page splits because each new value inserts at a random position, fragmenting the index. UUID v7 solves this — its timestamp prefix means consecutive inserts cluster at the rightmost leaf, the same behaviour as auto-increment. See UUID Database Primary Keys video walkthrough and the full UUID in Databases guide.
Should I use v4 or v7?
Use v7 for database primary keys (time-sortable, index-friendly) and v4 for anything where creation order could leak information, like tokens or share links.