nanoid
pg_random_id
Our great sponsors
nanoid | pg_random_id | |
---|---|---|
82 | 1 | |
23,140 | 5 | |
- | - | |
8.3 | 0.0 | |
12 days ago | about 4 years ago | |
JavaScript | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nanoid
- Nano ID Collision Calculator
-
Why we chose Bun
Our API is in node. And God, how I suffered to import nanoid in an esmodule project. I had to vendor it, since using a previous version was not ideal. With bun, we can no longer worry about that. Just import what you need and done.
-
UUIDv7 is coming in PostgreSQL 17
No thread about UUID is complete without a plug for NanoID! https://github.com/ai/nanoid/blob/main/README.md
-
Building a File Storage With Next.js, PostgreSQL, and Minio S3
Generate a unique file name using the nanoid library.
-
Building a Multi-Tenant App with FastAPI, SQLModel, and PropelAuth
The syntax should read similar to SQL itself. We’re using a Python port of nanoid to generate our IDs. There’s only one thing missing… how do we actually create the table?
-
You Don't Need UUID
I usually go for Nano Id for new projects https://github.com/ai/nanoid
-
Enhance Your Web Apps: Best JS Libraries 🔧
Nano ID
-
Analyzing New Unique Identifier Formats (UUIDv6, UUIDv7, and UUIDv8) (2022)
In another comment I mentioned I use nanoid in my projects now. It has a default space of 64^21 and has an a page where you can play with key lengths and alphabet sizes and see the probability of collisions :
https://zelark.github.io/nano-id-cc/
At the default 64 character alphabet with a 21 character key length it would take ~41 million years in order to have a 1% probability of at least one collision if you generated 1000 ids per second.
-
How I use Nano ID in Rails
Using randomly generated IDs like Nano ID could be a good alternative, however, as a developer, we must understand what Nano ID really does in our application. Defining the number of characters in the generated IDs is also important, to help with that Nano ID has a Collision Calculator to give us how many years in order to have a 1% probability of collision.
-
How debugging for accessibility helped me finally understand useRef
IDs used here for buttons and tasks must be unique to work correctly. This is ensured by using the nanoid package, which automatically generates unique ids.
pg_random_id
-
So Clubhouse violated one fundamental concept of API architecture. That not to expose numerically incrementing unique identifiers.
Or, my favorite - https://github.com/conjurinc/pg_random_id - map integer keys to a different, apparently random id using a Feistel cypher
What are some alternatives?
snowflake - Snowflake is a network service for generating unique ID numbers at high scale with some simple guarantees.
hscuid - Collision-resistant IDs for horizontal scaling
ksuid - K-Sortable Globally Unique IDs
typedorm - Strongly typed ORM for DynamoDB - Built with the single-table-design pattern in mind.
jest - Delightful JavaScript Testing.
Numeral-js - A javascript library for formatting and manipulating numbers.
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
effector-react - Business logic with ease ☄️
repeating - Repeat a string - fast
matcher - Simple wildcard matching
Cypress - Fast, easy and reliable testing for anything that runs in a browser.