GitHub - rafaelsales/ulid: Universally Unique Lexicographically Sortable Identifier implementation for Ruby (original) (raw)

🚨 Please hold on

If you're starting a new project with a empty database, use UUID v7 instead.

If you’re trying to address database slowness caused by non-time-ordered UUIDs, such as UUIDv4, use UUIDv7 instead.

➡️ Read more at:


Ruby Gem Downloads GitHub License

Universally Unique Lexicographically Sortable Identifier implementation for Ruby

Official specification page: https://github.com/ulid/spec

ulid

Universally Unique Lexicographically Sortable Identifier

UUID can be suboptimal for many uses-cases because:

Instead, herein is proposed ULID:

Installation

Usage

require 'ulid'

ULID.generate # 01ARZ3NDEKTSV4RRFFQ69G5FAV

I want to generate a ULID using an arbitrary timestamp

You can optionally pass a Time instance to ULID.generate to set an arbitrary timestamp component, i.e. the prefix of the ULID.

time_t1 = Time.now ulid = ULID.generate(time_t1)

I want to generate a ULID using an arbitrary suffix, i.e. without the randomness component

You can optionally pass a 80-bit hex-encodable String on the argument suffix to ULID.generate. This will replace the randomness component by the suffix provided. This allows for fully deterministic ULIDs.

require 'securerandom'

time = Time.now an_event_identifier = SecureRandom.uuid ulid1 = ULID.generate(time, suffix: an_event_identifier) ulid2 = ULID.generate(time, suffix: an_event_identifier) ulid1 == ulid2 # true

Specification

Below is the current specification of ULID as implemented in this repository. Note: the binary format has not been implemented.

 01AN4Z07BY      79KA1307SR9X4MV3

|----------|    |----------------|
 Timestamp          Randomness
  10 chars           16 chars
   48bits             80bits
   base32             base32

Components

Timestamp

Randomness

Sorting

The left-most character must be sorted first, and the right-most character sorted last. The default ASCII order is used for sorting.

Binary Layout and Byte Order

The components are encoded as 16 octets. Each component is encoded with the Most Significant Byte first (network byte order).

0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      32_bit_uint_time_high                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|     16_bit_uint_time_low      |       16_bit_uint_random      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                       32_bit_uint_random                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                       32_bit_uint_random                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

String Representation

ttttttttttrrrrrrrrrrrrrrrr

where
t is Timestamp
r is Randomness

Test Suite

Credits and references: