Bullet Train Has UUID

URL-friendly, Base32-encoded UUIDs for Rails models

uuid_v7 enables UUID V7 as primary keys in Rails, optimized for Mysql and Sqlite, with efficient migration and integration features.

Secure, collision-resistant ids optimized for horizontal scaling and performance.Next generation UUIDs. Need unique ids in your app? Forget UUIDs which often collide in large apps.Use Cuid2, instead.

Hides sequential primary key counts without resorting to UUIDs or GUIDs.

UUID V4 compliant timestamp uuid where also the string representation is correctly sorted by timestamp

RSpec UUID matcher

A fast Ruby implementation of UUID versions 4, 6, 7, and 8 🪪

Stop hitting the DB with every secure-token submission. Encoded Tokens have the ID, or UUID, encoded within the token itself - increasing both security and performance. Coded in plain Ruby, EncodedToken is framework agnostic.

Tranlates Wodbys instance UUIDs into instance names

Convert Integer ID or UUID String to/from Base58 String; Generate random Base58 String

UUID attribute for ActiveRecord

UUID "version 6" implementation in Ruby

Implementation of UUID v7

This extends shoulda-matchers to allow validating binary uuids in models.

This gem allows you to create unique readable fantasy names as identifiers for your active record objects. You can also define multiple identifier columns and alternatively use a UUID or Devise.friendly_token as identifier.

FriendlyUUID is a Rails gem that shortens your UUID records' URLs. What once was 758d633c-61d4-4dfc-ba52-b7b498971097 becomes 758d. FriendlyUUID does not introduce any new state to your models, even under the hood. FriendlyUUID URLs are exactly as unique as they need to be. The first record will be one character. Would-be collisions expand to two characters, and so on. FriendlyUUID is inspired by friendly_id, but is focused on being lightweight and specific to models with UUID primary keys.

Typed UUIDs 2 bytes are reserved in the UUID for the class enum

fast uuid generation and parsing library

Online logging solution (like [Datadog](https://www.datadoghq.com)) have drastically transform the way we log. An app will nowdays logs dozen (hundred) of logs per requests. The issue is often to correlate this logs, with the initiating request (or job) and add shared metadata on this logs. Here come `ContextualizedLogs`. The main idea is to enhance your logs from your controller (including `ContextualizedController`, which use a before action), which will add the params to your logs (and some metadata about the request itself, like `request.uuid`). This metadata are stored in a `ActiveSupport::CurrentAttributes` which is a singleton (reset per request). Each subsequent logs in this thread (request) will also be enriched with this metadata, making it easier to find all the logs associated with a request (`uuid`, `ip`, `params.xxx`). On top of this, logs can also be enriched by the ActiveRecord model they use (`create` or `find`) (models including `ContextualizedModel`). So any time a contextualized model is created or find, some metadata related to the model (`id`, ...) will also be added to the logs. Allowing you to find all logs which "touched" this models.