Key database size for key expansion? (without loss of performance)

We have a database table that will be 10 million records. We do not want to use auto_increment, because it will allow our users to find out how many records we have. We do not want to disclose this to our competitors. The problem I see is that using a UUID or something similar will kill query performance.

for example, this is no-no: http://domain.com/widgets?id=34345

because competitors can crawl the site to determine how many widgets we have. Should this business protection be handled at the application level or is it normal to handle it at the database level? What do most people do in this situation? The database we use is postgres, but I assume that the solution is still an agnostic of the database.

+3
source share
2 answers

GUID . , , . , GUID, , . GUID . 4 , .

120 10 , . GUID , ?

+3

URL- slug, slug , , , URL-, http://example.com/awesome-blue-widget. , , .. - slugify , , , .

[a-z0-9-]+. , , -.

+2

All Articles