.net: Avoid Using Guid.createversion7
Postedabout 2 months ago
gist.github.comTechstory
calmnegative
Debate
20/100
Guid.netDatabase Optimization
Key topics
Guid
.net
Database Optimization
The .NET 9+ Guid.CreateVersion7 method is claimed to be RFC 9562 compliant but actually causes database index fragmentation due to its endianness, contrary to its intended purpose.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
N/A
Peak period
1
Start
Avg / period
1
Key moments
- 01Story posted
Nov 12, 2025 at 8:12 AM EST
about 2 months ago
Step 01 - 02First comment
Nov 12, 2025 at 8:12 AM EST
0s after posting
Step 02 - 03Peak activity
1 comments in Start
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 12, 2025 at 8:12 AM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Discussion (1 comments)
Showing 1 comments
sdrapkinAuthor
about 2 months ago
Guid.CreateVersion7 in .NET 9+ claims RFC 9562 compliance but violates its big-endian requirement for binary storage. This causes the same database index fragmentation that v7 UUIDs were designed to prevent. Testing with 100K PostgreSQL inserts shows rampant fragmentation (35% larger indexes) versus properly-implemented sequential GUIDs.
View full discussion on Hacker News
ID: 45899718Type: storyLast synced: 11/17/2025, 6:02:11 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.