Switch from UUIDv4 to NanoID #71
Merged
Conversation
This file contains 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
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.
Overview
There have been several articles discussing the performance detriments that uuid4 present when they are used as the primary key. These include being difficult to index, slowing down insert operations, and not being URL friendly.
There have also been concerns about API routes becoming very large due to the nested objects in Honcho. To address these concerns we are using a
int8auto-incrementing value for the primary key of the database tables and then exposing apublic_idvalue that maps to a NanoIDThe end user has no concept of the internal ID at all and it is purely used for internal tracking and performance
Sources
Tracking
Fixes dev-402
Contains changes for dev-435