UUID vs. Sequential ID as Primary

From: <ahmed.fikri_at_t-online.de>
Date: Thu, 11 Apr 2024 06:37:20 +0200 (CEST)
Message-ID: <1712810240714.106912.72c6938f73f46d787d76d6b54845aae3859bf0cc_at_spica.telekom.de>

Once more, a question about fundamentals:

In several Hibernate projects, I've observed developers leaning towards using UUIDs as primary keys instead of numerical values. This preference likely stems from the avoidance of sequences for numerical primary keys, which necessitate round trips to the database after each insertion. Additionally, there's a concern about potential contention with sequences, and some developers may prefer to avoid predictability in the next generated value. Personally, I remain skeptical about the widespread use of UUIDs due to their larger storage footprint (both in tables and indexes) compared to numerical IDs. Numeric IDs also offer benefits in issue analysis. However, it's worth noting that Hibernate employs algorithms to minimize round trips to the database, effectively reducing their impact. Could you please share your experience and preference? What choice would you make?

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Apr 11 2024 - 06:37:20 CEST

This message: [ Message body ]
Next message: Stefan Koehler: "Re: Increased runtime and 4 xids for one insert"
Previous message: Jonathan Lewis: "Re: Increased runtime and 4 xids for one insert"
Next in thread: Mladen Gogala: "Re: UUID vs. Sequential ID as Primary"
Reply: Mladen Gogala: "Re: UUID vs. Sequential ID as Primary"
Reply: Peter Gram: "Re: UUID vs. Sequential ID as Primary"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message