nanoid VS find-my-way

No thread about UUID is complete without a plug for NanoID! https://github.com/ai/nanoid/blob/main/README.md

Generate a unique file name using the nanoid library.

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?

I usually go for Nano Id for new projects https://github.com/ai/nanoid

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.

I’ve started using nanoid for generated ids. Here is the JavaScript version:

https://github.com/ai/nanoid

Some info from that page:

- Safe. It uses hardware random generator. Can be used in clusters.

- Short IDs. It uses a larger alphabet than UUID (A-Za-z0-9_-). So ID size was reduced from 36 to 21 symbols.

- Portable. Nano ID was ported to 20 programming languages.

Introducing Nano ID. Nano ID is a tiny, URL-friendly, and unique string ID generator. Nano ID is a library for generating random IDs that still have probability of duplicate IDs. However, this probability is extremely small and it is based on the rules you defined. Here are the features of Nano ID:

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.

bin: Sometimes it may be desired or even crucial for a package to provide a command line interface, take a testing framework like jest as an example. NPM allows packages to publish executable binaries for this purpose, and as a convention they're usually placed in this directory. Example from nanoid.

The development began two months ago and we have not encountered any scaling issues yet, as the majority of users self-host. Therefore, our priority was focused on building apps. Is there anything you believe we should consider?

You are correct, repeating the same index twice is a mistake. That's why I love open source.

We are using nano id (https://www.npmjs.com/package/nanoid) for all entities, It's stored as varchar in the database.

I found libraries in other programming languages that use this approach : matchit (Rust), find-my-way (Javascript), fasthttp (Go) But, curiously, no one in PHP. That's why I decided to bring my contribution to have the same approach in PHP.

Looking at the benchmarks, Fastify is the clear winner among other Nodejs frameworks. It has faster routing, JSON handling with faster rendering and a bunch of ready-made plugins.