firebase.database () multiple instances
up vote
1
down vote
favorite
I am using firebase realtime database and I was wondering which is a better pattern regarding
firebase.database()
is it considered bad practice to have multiple instances of this. Is it better if I have a single instance of the database which is exported within the node app. Or is it basically the same thing to create a new instance for every single action creator file.
import * as firebase from 'firebase';
firebase.initializeApp(config);
export const provider = new firebase.auth.GoogleAuthProvider();
export const auth = firebase.auth();
export default firebase;
I have this approach for the firebase app instance and I am unsure if a similar pattern is required for the database instance as well. There weren't any specifications within the firebase docs.
node.js firebase firebase-realtime-database
add a comment |
up vote
1
down vote
favorite
I am using firebase realtime database and I was wondering which is a better pattern regarding
firebase.database()
is it considered bad practice to have multiple instances of this. Is it better if I have a single instance of the database which is exported within the node app. Or is it basically the same thing to create a new instance for every single action creator file.
import * as firebase from 'firebase';
firebase.initializeApp(config);
export const provider = new firebase.auth.GoogleAuthProvider();
export const auth = firebase.auth();
export default firebase;
I have this approach for the firebase app instance and I am unsure if a similar pattern is required for the database instance as well. There weren't any specifications within the firebase docs.
node.js firebase firebase-realtime-database
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am using firebase realtime database and I was wondering which is a better pattern regarding
firebase.database()
is it considered bad practice to have multiple instances of this. Is it better if I have a single instance of the database which is exported within the node app. Or is it basically the same thing to create a new instance for every single action creator file.
import * as firebase from 'firebase';
firebase.initializeApp(config);
export const provider = new firebase.auth.GoogleAuthProvider();
export const auth = firebase.auth();
export default firebase;
I have this approach for the firebase app instance and I am unsure if a similar pattern is required for the database instance as well. There weren't any specifications within the firebase docs.
node.js firebase firebase-realtime-database
I am using firebase realtime database and I was wondering which is a better pattern regarding
firebase.database()
is it considered bad practice to have multiple instances of this. Is it better if I have a single instance of the database which is exported within the node app. Or is it basically the same thing to create a new instance for every single action creator file.
import * as firebase from 'firebase';
firebase.initializeApp(config);
export const provider = new firebase.auth.GoogleAuthProvider();
export const auth = firebase.auth();
export default firebase;
I have this approach for the firebase app instance and I am unsure if a similar pattern is required for the database instance as well. There weren't any specifications within the firebase docs.
node.js firebase firebase-realtime-database
node.js firebase firebase-realtime-database
asked Nov 19 at 22:43
Saccarab
1029
1029
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
Every time you call one of the product methods on the firebase
object that you get from the import, it will give you exactly the same object in return. So, every time you call firebase.auth()
, you'll get the same thing back, and every time you call firebase.database()
, you'll get the same thing. How you want to manage those instances is completely your preference.
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
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',
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%2f53383715%2ffirebase-database-multiple-instances%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Every time you call one of the product methods on the firebase
object that you get from the import, it will give you exactly the same object in return. So, every time you call firebase.auth()
, you'll get the same thing back, and every time you call firebase.database()
, you'll get the same thing. How you want to manage those instances is completely your preference.
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
add a comment |
up vote
3
down vote
accepted
Every time you call one of the product methods on the firebase
object that you get from the import, it will give you exactly the same object in return. So, every time you call firebase.auth()
, you'll get the same thing back, and every time you call firebase.database()
, you'll get the same thing. How you want to manage those instances is completely your preference.
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Every time you call one of the product methods on the firebase
object that you get from the import, it will give you exactly the same object in return. So, every time you call firebase.auth()
, you'll get the same thing back, and every time you call firebase.database()
, you'll get the same thing. How you want to manage those instances is completely your preference.
Every time you call one of the product methods on the firebase
object that you get from the import, it will give you exactly the same object in return. So, every time you call firebase.auth()
, you'll get the same thing back, and every time you call firebase.database()
, you'll get the same thing. How you want to manage those instances is completely your preference.
answered Nov 19 at 23:03
Doug Stevenson
68.2k880100
68.2k880100
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
add a comment |
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
I was just wondering if there are any downsides to have multiple instances of a database instance
– Saccarab
Nov 20 at 0:24
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
My answer is saying that there are not actually multiple instances. There is one instance, and you're holding a reference to it in multiple places. Each reference takes a few bytes.
– Doug Stevenson
Nov 20 at 0:31
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53383715%2ffirebase-database-multiple-instances%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