Best way to generate arbitrary hash about hashids HOT 4 CLOSED

1. Are you sure you need to store them in the database (as opposed to generating on the fly)? If yes, you'll need to do an update once you get the numerical id.
2. Are you generating hundreds of thousands ids per second? If no, why are you worrying about speed? This library is already crazy fast.

from hashids.

Interesting. It didn’t occur to me to generate them on the fly. Is encoding/decoding on the fly performant enough to do in a pretty high volume site? Perhaps 1000 requests per minute?

Thanks!

On May 4, 2016, at 3:45 PM, Ivan Akimov [email protected] wrote:

Are you sure you need to store them in the database (as opposed to generating on the fly)? If yes, you'll need to do an update once you get the numerical id.
Are you generating hundreds of thousands ids per second? If no, why are you worrying about speed? This library is already crazy fast.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #65 (comment)

from hashids.

Yes, it is. You could always time it to see if it fits your needs.

Benefits of on-the-fly:

• Can decode back to ID and select directly by it (which is usually already indexed)
• Don't need overhead of maintaining extra column/field in db

Benefits of storing in db:

• Easy to move away to another library later on
• Easy to modify "hashes" to something else
• Easier to debug (select by)

from hashids.

Thanks!

On May 5, 2016, at 10:02 AM, Ivan Akimov [email protected] wrote:

Yes, it is. You could always time it to see if it fits your needs.

Benefits of on-the-fly:

Can decode back to ID and select directly by it (which is usually already indexed)
Don't need overhead of maintaining extra column/field in db
Benefits of storing in db:

Easy to move away to another library later on
Easy to modify "hashes" to something else
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #65 (comment)

from hashids.