Firebase performance, which approach is better?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
Imagine a database structured this way:
If I need to display only a few of this info, not all of them, which approach is better?
Approach 1
download the whole node with:
getInfo(userId){
firebase.database().ref("userinfo/" + userId)
.on("value", (info => {
//code here
}))
}
and, once I have the whole info, show only what I need
or
Approach 2
download only the nodes that I need, this would imply a few calls running at the same time, example:
getInfoByNode(userId){
firebase.database().ref("userinfo/" + userId + "/name")
.on("value", (name => {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/email")
.on("value", (email=> {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/phone")
.on("value", (phone=> {
//code here
}))
}
performance firebase firebase-realtime-database
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
add a comment |
0
Imagine a database structured this way:
If I need to display only a few of this info, not all of them, which approach is better?
Approach 1
download the whole node with:
getInfo(userId){
firebase.database().ref("userinfo/" + userId)
.on("value", (info => {
//code here
}))
}
and, once I have the whole info, show only what I need
or
Approach 2
download only the nodes that I need, this would imply a few calls running at the same time, example:
getInfoByNode(userId){
firebase.database().ref("userinfo/" + userId + "/name")
.on("value", (name => {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/email")
.on("value", (email=> {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/phone")
.on("value", (phone=> {
//code here
}))
}
performance firebase firebase-realtime-database
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
1
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like/userinfo/${userId}/detailsanddetailscould be an object{ name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.
– sketchthat
Nov 29 '18 at 4:34
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
2
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
1
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39
add a comment |
0
0
0
Imagine a database structured this way:
If I need to display only a few of this info, not all of them, which approach is better?
Approach 1
download the whole node with:
getInfo(userId){
firebase.database().ref("userinfo/" + userId)
.on("value", (info => {
//code here
}))
}
and, once I have the whole info, show only what I need
or
Approach 2
download only the nodes that I need, this would imply a few calls running at the same time, example:
getInfoByNode(userId){
firebase.database().ref("userinfo/" + userId + "/name")
.on("value", (name => {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/email")
.on("value", (email=> {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/phone")
.on("value", (phone=> {
//code here
}))
}
performance firebase firebase-realtime-database
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
Imagine a database structured this way:
If I need to display only a few of this info, not all of them, which approach is better?
Approach 1
download the whole node with:
getInfo(userId){
firebase.database().ref("userinfo/" + userId)
.on("value", (info => {
//code here
}))
}
and, once I have the whole info, show only what I need
or
Approach 2
download only the nodes that I need, this would imply a few calls running at the same time, example:
getInfoByNode(userId){
firebase.database().ref("userinfo/" + userId + "/name")
.on("value", (name => {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/email")
.on("value", (email=> {
//code here
}))
firebase.database().ref("userinfo/" + userId + "/phone")
.on("value", (phone=> {
//code here
}))
}
performance firebase firebase-realtime-database
performance firebase firebase-realtime-database
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
asked Nov 29 '18 at 4:24
F. RusconiF. Rusconi
266
266
1
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like/userinfo/${userId}/detailsanddetailscould be an object{ name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.
– sketchthat
Nov 29 '18 at 4:34
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
2
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
1
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39
add a comment |
1
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like/userinfo/${userId}/detailsanddetailscould be an object{ name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.
– sketchthat
Nov 29 '18 at 4:34
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
2
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
1
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39
1
1
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like
/userinfo/${userId}/details and details could be an object { name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.– sketchthat
Nov 29 '18 at 4:34
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like
/userinfo/${userId}/details and details could be an object { name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.– sketchthat
Nov 29 '18 at 4:34
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
2
2
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
1
1
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39
add a comment |
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f53531813%2ffirebase-performance-which-approach-is-better%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53531813%2ffirebase-performance-which-approach-is-better%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
1
Be careful when storing BSB/Account Number information, ensure that your business is PCI DDS compliant as required. Also if you know you're always fetching those details you could break the data into another sub object like
/userinfo/${userId}/detailsanddetailscould be an object{ name, email, phone }. Meaning you can access their details with one request instead of three and without the bloat.– sketchthat
Nov 29 '18 at 4:34
Thanks for your answer. We are storing that info in order to pay users. We are using Stripe for payments from users to us. Do we still need to be PCI DDS compliant? Also, your idea is a very good one. If you had to choose between the two approaches above, which one would you choose?
– F. Rusconi
Nov 29 '18 at 5:00
2
It looks like you're trying to optimize something that doesn't need any optimization. You're not dealing with very much data here. The difference between the two methods is not significant for the size of data here. If you really need to optimize this, you should perform your own benchmarks and compare the results.
– Doug Stevenson
Nov 29 '18 at 9:15
1
Offtopic: Yes, you still need compliance to store the information regardless of it being for credits or debits. I believe Stripe can tokenlize this data for you - and they are compliant. So you can look into hosting the BSB/Account with them and get back a token which can be used to credit customers accounts.
– sketchthat
Nov 29 '18 at 23:39