How to design a large-capacity registration system?

1. There is a game company's registration system, and the user registration information is stored in the user information table;

2. There are only two fields in the user information table: ID and game nickname, where ID is the primary key, which is generated according to certain rules; the user nickname is the information that the user needs to enter when registering, and cannot be modified after input, and cannot be repeated (that is, the full server only);

3. Now the planned number of registered users has reached the level that needs to be divided into tables. If the user information table needs to be divided into 100 tables by ID;

Now if you are asked to design the business process of registration, how to design to meet the above requirements?

 

refer to:

https://mp.weixin.qq.com/s?__biz=MjM5ODYxMDA5OQ==&mid=2651960032&idx=1&sn=1f818d415842d544dc33ab78e8adffea&chksm=bd2d073c8a5a8e2a38e7534d57ca0cad613893b9c3b578a220c4beef5d7495c5a1569cf4768e&mpshare=1&scene=1&srcid=0512JL4w0KF1KvmZGgWjXcgC&pass_ticket=ZsRUbWMTOonZerLQXapUIXq6XZN2j9k8lAVKkXUEH9N3goWvoA8oOqe%2F6OIyg38C#rd

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326441264&siteId=291194637