Summary

We need to transition from ULID to UUIDv7 for time-ordered identifiers across our system, as outlined in ADR-0009.

Description

Description

We need to transition from ULID to UUIDv7 for time-ordered identifiers across our system, as outlined in ADR-0009. UUIDv7 provides similar benefits to ULID while offering better system compatibility, standardization, and reduced custom code maintenance.

Current implementation uses ULID for time-ordered identifiers, which requires special handling and custom code. UUIDv7 (RFC 9562) provides the same benefits with better system compatibility and standardization.

Goal

Standardize our unique identifier strategy by:

• Using UUIDv7 for time-ordered identifiers
• Using UUIDv4 for type-specific identifiers
• Removing ULID dependencies
• Simplifying database operations with native UUID types

Related PR

• ADR-0009: UUIDv7 vs ULID docs: Adds ADR on the migration to UUID7 #1370

Acceptance Criteria

Documentation

• Update API documentation to specify UUID format requirements
• Document when to use UUIDv4 vs UUIDv7

Implementation

• Identify all ULID usage in the codebase
• Create UUIDv7 generation utilities
• Update database schemas to use UUID types
• Create data migration scripts
• Update existing ULID implementations to UUIDv7
• Update test cases to reflect UUID usage

Testing

• Verify UUIDv7 generation meets time-ordering requirements
• Test database operations with new UUID types
• Validate data migration scripts
• Ensure backward compatibility during transition
• Performance testing of UUID operations

Resources

• ADR-0009: UUIDv7 vs ULID
• RFC 9562 - UUIDv7 Specification
• ULID Specification