universally unique identifier
UUID 표준에 따라 이름을 부여하면 고유성을 완벽하게 보장할 수는 없지만 실제 사용상에서 중복될 가능성이 거의 없다고 인정되기 때문에 ID고유성이 필요한 MSA에서 많이 사용되고 있다

5개의 그룹을 하이픈으로 구분한다. 이를테면 다음과 같다.
고유성을 완벽하게 보장하려면 중앙관리시스템이 있어서 일련번호를 부여해 주면 간단하지만 동시다발적이고 독립적으로 개발되고 있는 시스템들의 경우 중앙관리시스템은 불가능하다
개발주체가 스스로 이름을 짓도록 하되 고유성을 충족할 수 있는 방법이 필요하다. 이를 위하여 탄생한 것이 범용고유식별자(UUID)이며 국제기구에서 표준으로 정하고 있다.
UUID Versions
UUID Usages
8 versions
TIL: 8 versions of UUID and when to use them | nicole@web
About a month ago1, I was onboarding a friend into one of my side project codebases and she asked me why I was using a particular type of UUID.
I'd heard about this type while working on that project, and it's really neat.
So instead of hogging that knowledge for just us, here it is: some good uses for different versions of UUID.
https://www.ntietz.com/blog/til-uses-for-the-different-uuid-versions/
New UUID Formats
This document presents new time-based UUID formats which are suited for use as a database key. A common case for modern applications is to create a unique identifier for use as a primary key in a database table. This identifier usually implements an embedded timestamp that is sortable using the monotonic creation time in the most significant bits. In addition the identifier is highly collision resistant, difficult to guess, and provides minimal security attack surfaces. None of the existing UUID versions, including UUIDv1, fulfill each of these requirements in the most efficient possible way. This document is a proposal to update with three new UUID versions that address these concerns, each with different trade-offs.
https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-01.html#name-uuidv7-layout-and-bit-order
UUID vs Crypto.randomUUID vs NanoID
Which is the best unique uuid generator that fits your project? Having a unique identifier is an important requirement in many applications today. The universally unique identifiers are just 128-bit pieces of data, that are displayed as (128/4) = 32 hexadecimal digits.
https://medium.com/p/uuid-vs-crypto-randomuuid-vs-nanoid-313e18144d8c


Seonglae Cho