Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

用户系统设计 #37

Open
cena009 opened this issue Nov 13, 2020 · 6 comments
Open

用户系统设计 #37

cena009 opened this issue Nov 13, 2020 · 6 comments

Comments

@cena009
Copy link

cena009 commented Nov 13, 2020

看了楼主数据库设计，抽象了accout的表，与登录相关的账号表都在里面，但是这也有点不好，如果用户数很多，比如多个公司的员工账户都写到这个表，是不是会慢，个人感觉还是分开好点，减少单表的压力，交流交流
@cena009
Copy link
Author

cena009 commented Nov 13, 2020

抽象的思路是挺好的，但是用户量一旦上来了，单表就会有压力了

@TIGERB
Copy link
Member

TIGERB commented Nov 13, 2020

用户数很多

一般就分库分表了

简单可以使用mycat之类的

@xushuhui
Copy link
Contributor

今天在写skrshop接口的时候忽然想到抽象出account_user表相当强行关联c端用户和B端后台员工，这样是否有必要，如果公司主推c端产品，这样的关联的意义是什么？从业务的角度

@TIGERB
Copy link
Member

TIGERB commented Feb 24, 2021 •
edited
Loading

比如给 员工发C端产品优惠券等

@xianyuyixia
Copy link

请问下楼主，现在的设计是否支持多公众号多小程序的情况，假如都绑定到同一个开放平台，unionid可以存在第三方用户信息表，那每个公众号或者小程序的openid是存放到那个表好

@TIGERB
Copy link
Member

TIGERB commented Mar 10, 2023

目前确实没考虑小程序哈

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@TIGERB @xushuhui @cena009 @xianyuyixia