You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is some negatives to performance associated with UUIDv4 keys due to their use of randomness. ULID and UUIDv7 offer some improvements over this which improve indexing performance.
Our current use of UUIDv4, however, is quite limited and only really used to prevent basic enumeration attacks for a select few endpoints, so the effort involved may not be worth it.
As far as i understand both are able to be used as a drop in replacement for the 128 bit uuid type, but needs more investigation/testing to verify this claim.
Very good chance this is not worth the effort involved due to our, currently at least, limited rows using these as primary keys.
The text was updated successfully, but these errors were encountered:
There is some negatives to performance associated with UUIDv4 keys due to their use of randomness. ULID and UUIDv7 offer some improvements over this which improve indexing performance.
Our current use of UUIDv4, however, is quite limited and only really used to prevent basic enumeration attacks for a select few endpoints, so the effort involved may not be worth it.
As far as i understand both are able to be used as a drop in replacement for the 128 bit uuid type, but needs more investigation/testing to verify this claim.
Very good chance this is not worth the effort involved due to our, currently at least, limited rows using these as primary keys.
The text was updated successfully, but these errors were encountered: