Database design for user account
I'm building SaaS platform. One user can only have one account (or user account). Which means one user has email, password, balance, tier plan.
What I'm confused is that should I separate the user account setting and the tier/balance data?
Should I make it 2 separate models: User (email, password) and Account (balance, tier, user_id)?
or make it one model: UserAccount(email, password, balance, tier, user_id) ?
I thought user model won't go through many changes in structure since its just for authentication.. But, for the account maybe there's some change in the future
node.js mongodb mongoose database-design
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
add a comment |
I'm building SaaS platform. One user can only have one account (or user account). Which means one user has email, password, balance, tier plan.
What I'm confused is that should I separate the user account setting and the tier/balance data?
Should I make it 2 separate models: User (email, password) and Account (balance, tier, user_id)?
or make it one model: UserAccount(email, password, balance, tier, user_id) ?
I thought user model won't go through many changes in structure since its just for authentication.. But, for the account maybe there's some change in the future
node.js mongodb mongoose database-design
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
add a comment |
I'm building SaaS platform. One user can only have one account (or user account). Which means one user has email, password, balance, tier plan.
What I'm confused is that should I separate the user account setting and the tier/balance data?
Should I make it 2 separate models: User (email, password) and Account (balance, tier, user_id)?
or make it one model: UserAccount(email, password, balance, tier, user_id) ?
I thought user model won't go through many changes in structure since its just for authentication.. But, for the account maybe there's some change in the future
node.js mongodb mongoose database-design
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
I'm building SaaS platform. One user can only have one account (or user account). Which means one user has email, password, balance, tier plan.
What I'm confused is that should I separate the user account setting and the tier/balance data?
Should I make it 2 separate models: User (email, password) and Account (balance, tier, user_id)?
or make it one model: UserAccount(email, password, balance, tier, user_id) ?
I thought user model won't go through many changes in structure since its just for authentication.. But, for the account maybe there's some change in the future
node.js mongodb mongoose database-design
node.js mongodb mongoose database-design
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
asked Nov 14 '18 at 16:43
Terry DjonyTerry Djony
497822
497822
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Ideal way should be to have Two Different Collections, but in your case when you're dealing with MongoDB (NoSQL DB) you should focus on Denormalization.
i.e. to keep avoid more collections & relations.
So, Having one model: UserAccount(email, password, balance, tier, user_id) is the ideal choice.
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
add a comment |
You should split. That's called separation of concerns. You have a model for authentication and another for user details. you can add a foreign key from account to user.
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305016%2fdatabase-design-for-user-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ideal way should be to have Two Different Collections, but in your case when you're dealing with MongoDB (NoSQL DB) you should focus on Denormalization.
i.e. to keep avoid more collections & relations.
So, Having one model: UserAccount(email, password, balance, tier, user_id) is the ideal choice.
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
add a comment |
Ideal way should be to have Two Different Collections, but in your case when you're dealing with MongoDB (NoSQL DB) you should focus on Denormalization.
i.e. to keep avoid more collections & relations.
So, Having one model: UserAccount(email, password, balance, tier, user_id) is the ideal choice.
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
add a comment |
Ideal way should be to have Two Different Collections, but in your case when you're dealing with MongoDB (NoSQL DB) you should focus on Denormalization.
i.e. to keep avoid more collections & relations.
So, Having one model: UserAccount(email, password, balance, tier, user_id) is the ideal choice.
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
Ideal way should be to have Two Different Collections, but in your case when you're dealing with MongoDB (NoSQL DB) you should focus on Denormalization.
i.e. to keep avoid more collections & relations.
So, Having one model: UserAccount(email, password, balance, tier, user_id) is the ideal choice.
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
answered Nov 15 '18 at 12:04
Shishir SonekarShishir Sonekar
11518
11518
add a comment |
add a comment |
You should split. That's called separation of concerns. You have a model for authentication and another for user details. you can add a foreign key from account to user.
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
add a comment |
You should split. That's called separation of concerns. You have a model for authentication and another for user details. you can add a foreign key from account to user.
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
add a comment |
You should split. That's called separation of concerns. You have a model for authentication and another for user details. you can add a foreign key from account to user.
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
You should split. That's called separation of concerns. You have a model for authentication and another for user details. you can add a foreign key from account to user.
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
answered Nov 14 '18 at 21:09
Pedro SilvaPedro Silva
716215
716215
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
add a comment |
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
I'm using NoSQL MongoDB
– Terry Djony
Nov 15 '18 at 18:23
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305016%2fdatabase-design-for-user-account%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
