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

用户模块 #47

Open
ZeroMing opened this issue Apr 12, 2021 · 7 comments
Open

用户模块 #47

ZeroMing opened this issue Apr 12, 2021 · 7 comments

Comments

@ZeroMing
Copy link

有个点想请教一下：

  1. 账户服务的表设计，您这边的账户表应该都是在账户服务中维护吧，如果说我后面想做好几个系统的会员服务，
    是让账户服务统一维护
    还是让各自的会员服务去单独维护，仅仅引用一下账户服务的uid

  2. 如果是分库的，各个系统的会员信息表，是都放在账户服务的实例上，还是放到各自的数据库实例上
@TIGERB
Copy link
Member

TIGERB commented Apr 13, 2021

  1. 各自的会员服务去单独维护，仅仅引用一下账户服务的uid

  2. 基于现在业务量级和研发人员规模：

量级较小：同一个实例且不分库，但是表名前缀要显示的区分，方便未来分库。
量级还行：同一个实例但是分库
量级大：直接不同实例

@ZeroMing
Copy link
Author

  1. 各自的会员服务去单独维护，仅仅引用一下账户服务的uid
  2. 基于现在业务量级和研发人员规模：

量级较小：同一个实例且不分库，但是表名前缀要显示的区分，方便未来分库。
量级还行：同一个实例但是分库
量级大：直接不同实例

好的，谢谢~ 主要考虑会员这种业务属性，如果放在账号服务中，不是很合适，还是沉到各自的会员系统中。不过也要看实际的业务体谅

@TIGERB
Copy link
Member

TIGERB commented Apr 15, 2021

嗯嗯，是的

好的业务架构都是依据自身的环境决定和演变的。

@nanxing7
Copy link

员工离职了怎么处理

@TIGERB
Copy link
Member

TIGERB commented Oct 19, 2021

软删除？

@nanxing7
Copy link

软删除？

只能这么干了

@TIGERB
Copy link
Member

TIGERB commented Oct 19, 2021

嗯

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
3 participants
@TIGERB @ZeroMing @nanxing7