Storing millions of values in mapping variable

Question

Is it a good practice to store millions of values in a mapping variable for unique verification? For example, storing a customer name and unique number and later retrieve customer information from that unique number (like a sequence number).

Answer 1

Well, that's exactly what the standard ERC20 does. It stores all the balances, aka the people who own the token, in one mapping variable. This is actually a revealing fact for many people. When you send someone the tokens you own, fundamentally, only some values of an array are updated.

Therefore, it is safe for you to store your customers in a mapping. However, due to collisions, I wouldn't make the name the key. You could try a username.