docs: update UUID recommendation to v7 for better database performance#2219
Merged
soyuka merged 2 commits intoapi-platform:4.2from Nov 25, 2025
Merged
docs: update UUID recommendation to v7 for better database performance#2219soyuka merged 2 commits intoapi-platform:4.2from
soyuka merged 2 commits intoapi-platform:4.2from
Conversation
soyuka
approved these changes
Nov 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for the documentation reference!
I noticed the linked 2015 blog post advocates for UUIDv4, but doesn't mention the database performance implications that have become better understood since then.
UUIDv4's random nature can be detrimental to database performance: when inserted as a primary key into B-tree indexes (like MySQL InnoDB or PostgreSQL), random UUIDs can fall into any position in the index. This causes frequent page splits, index fragmentation, slower writes, and poor cache utilization.
Would you be open to recommending UUIDv7 instead? It maintains the benefits of UUIDs while avoiding these performance issues thanks to its time-ordered structure.