4 ms·
> For the majority of cases, a random ID remains the better option. If your ID is going to be exposed to a human you have to admit that random UUID's are kinda
by spookthesunset 4y ago
> For the majority of cases, a random ID remains the better option.
If your ID is going to be exposed to a human you have to admit that random UUID's are kinda clumsy.
One other pro to UUID's that I don't see discussed is you can generate them client side and be 99.9999999% assured that they won't collide when stored in the DB. I kinda forget our use case for this but I think it was to make "create" and "update" REST calls a lot easier.