For a simple practical example, it's awfully useful for a lot of systems to be able to generate UUIDs in an app while offline (think document creation, etc) and reconcile things later by shooting the blob of content off to the server, while knowing that you only need to handle the dance of getting IDs and updating stuff locally again in your error handling case.
Re:You Don't Need UUID
by emodendroket on Monday September 11, 2023 @01:28PM
(#37470548)
That’s an excellent point; that can end up being a bottleneck across many systems.
Re:You Don't Need UUID
by refulgentis on Monday September 11, 2023 @02:43PM
(#37471760)
What can?
Re:You Don't Need UUID
by marginalia_nu on Monday September 11, 2023 @03:01PM
(#37472075)
Unique ID generation.
Re:You Don't Need UUID
by emodendroket on Monday September 11, 2023 @03:35PM
(#37472576)
A service responsible for handing out UIDs.
No, it doesn't.
If you're using a central system to generate id's (UUID's or other), then you are indeed missing a lot of the benefits of UUID's and might as well use some other ID scheme.
The benefits of UUID are many systems can generate them, and your database can eventually accept them, all with a very high guarantee of uniqueness/no-collisions. Not to mention the other nice bits like non-sequential and non-enumerability.
Most modern databases have UUID/Binary types/functions to allow for more efficient storage/handling anyway.