Styjun

Why does it take longer to fly from London to Xi'an than to Beijing

Why was the ancient one so hesitant to teach Dr Strange the art of sorcery

What does this quote in Small Gods refer to?

What was the notion of limit that Newton used?

Is this state of Earth possible, after humans left for a million years?

Why did they go to Dragonstone?

Peculiarities in low dimensions or low order or etc

Why do the Avengers care about returning these items in Endgame?

How to get the IP of a user who executed a command?

is it permitted to swallow spit on a fast day?

When do you stop "pushing" a book?

What do "KAL." and "A.S." stand for in this inscription?

How to find the tex encoding of specific fonts?

Why should password hash verification be time consistent?

How to evaluate sum with one million summands?

Advantages/Disadvantages of Compiling as Both C and C++?

We are two immediate neighbors who forged our own powers to form concatenated relationship. Who are we?

How can a demonic viral infection spread throughout the body without being noticed?

What's the "magic similar to the Knock spell" referenced in the Dungeon of the Mad Mage adventure?

Need help replacing old cassette and chain

Why do Thanos' punches not kill Captain America or at least cause vital wounds?

Removing all characters except digits from clipboard

Extending Kan fibrations, without using minimal fibrations

spatiotemporal regression

Is it okay to create many instances of firebase realtime database (>20) in one project [closed]

Minimising Firebase realtime database traffic usageMultiple databases in Firebase projectConfusion related to firebase realtime database pricing modelFirebase Realtime Database: Fan-out costs and limitationsFirebase Realtime Database security concernCombining Firebase Auth with Firebase Realtime Database or Google Cloud Datastore?Is there a limit of databases per project in Firebase ? Is it possible to create them programmatically?Firebase Realtime Database - Scaling above 100.000 concurrent connectionsFirebase Load TestingMaximal nodes in a path with listeners or queries in firebase realtime database?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

2

I need some advice. We have an android app with million+ daily active users. We use firebase realtime database. As firebase realtime db has 100K connection limit, we had created 10 db instances and distributed the load equally. (All databases has same data, and we update db2-db10 using firebase functions, we write to default db first)


Now we are getting more users and 10 instances aren't enough. We need to create more. We're planning to create another 10DBs, is it fine to do so?
It feels weird to have so many instances so I'm just being careful if it's safe to do so. As db instance once created can't be deleted either.

firebase firebase-realtime-database

share|improve this question

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

closed as off-topic by Jay, thewaywewere, EdChum, dgknca, a_guest Mar 24 at 0:25

This question appears to be off-topic. The users who voted to close gave these specific reasons:

• "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Jay, a_guest


• "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – thewaywewere, EdChum, dgknca

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This sounds like a very specific use case. You should consider reaching out to Firebase support directly for direction on the best way to handle that many users/instances. They may also have input on an appropriate pricing program.
  
  – Jay
  Mar 23 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  firebaser here Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. If you still need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.
  
  – Frank van Puffelen
  Mar 23 at 14:10
  

  
  
  
  

add a comment | 

2

I need some advice. We have an android app with million+ daily active users. We use firebase realtime database. As firebase realtime db has 100K connection limit, we had created 10 db instances and distributed the load equally. (All databases has same data, and we update db2-db10 using firebase functions, we write to default db first)


Now we are getting more users and 10 instances aren't enough. We need to create more. We're planning to create another 10DBs, is it fine to do so?
It feels weird to have so many instances so I'm just being careful if it's safe to do so. As db instance once created can't be deleted either.

firebase firebase-realtime-database

share|improve this question

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

closed as off-topic by Jay, thewaywewere, EdChum, dgknca, a_guest Mar 24 at 0:25

This question appears to be off-topic. The users who voted to close gave these specific reasons:

• "Questions on professional server- or networking-related infrastructure administration are off-topic for Stack Overflow unless they directly involve programming or programming tools. You may be able to get help on Server Fault." – Jay, a_guest


• "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting." – thewaywewere, EdChum, dgknca

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This sounds like a very specific use case. You should consider reaching out to Firebase support directly for direction on the best way to handle that many users/instances. They may also have input on an appropriate pricing program.
  
  – Jay
  Mar 23 at 14:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  firebaser here Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. If you still need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.
  
  – Frank van Puffelen
  Mar 23 at 14:10
  

  
  
  
  

add a comment | 

I need some advice. We have an android app with million+ daily active users. We use firebase realtime database. As firebase realtime db has 100K connection limit, we had created 10 db instances and distributed the load equally. (All databases has same data, and we update db2-db10 using firebase functions, we write to default db first)


Now we are getting more users and 10 instances aren't enough. We need to create more. We're planning to create another 10DBs, is it fine to do so?
It feels weird to have so many instances so I'm just being careful if it's safe to do so. As db instance once created can't be deleted either.

firebase firebase-realtime-database

share|improve this question

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

share|improve this question

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

share|improve this question

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

edited Mar 23 at 10:23

Mayank Patel

2,96172746

edited Mar 23 at 10:23

Mayank Patel

2,96172746

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

asked Mar 23 at 9:52

Pablo EscobarPablo Escobar

426214

1 Answer
1

active

oldest

votes

2

firebaser here

There is no documented limit to the number of databases (often referred to as shards) you can have within a project. Each database essentially functions as a completely separate instance, so there isn't any reason to have a limit at all. As long as you can spread your users over the shards, it can scale infinitely.

That said: Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. You might be able to get by with much fewer shards.

But if you really need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.

share|improve this answer

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you so much @Frank van Puffelen, the fact that each database instance function separately is relaxing. Currently, we have created 20 db instances. Actually we want to stop using the previous db instances, as some developers are misusing those databases' data for their apps, the database structured is exposed and we can't put any kind of authentication for our apps' old version to run properly. So we planned when most the users will have moved to the new dbs, we'll discontinue them.
  
  – Pablo Escobar
  Mar 24 at 13:04
  

  
  
  
  

add a comment | 

2

firebaser here

There is no documented limit to the number of databases (often referred to as shards) you can have within a project. Each database essentially functions as a completely separate instance, so there isn't any reason to have a limit at all. As long as you can spread your users over the shards, it can scale infinitely.

That said: Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. You might be able to get by with much fewer shards.

But if you really need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.

share|improve this answer

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you so much @Frank van Puffelen, the fact that each database instance function separately is relaxing. Currently, we have created 20 db instances. Actually we want to stop using the previous db instances, as some developers are misusing those databases' data for their apps, the database structured is exposed and we can't put any kind of authentication for our apps' old version to run properly. So we planned when most the users will have moved to the new dbs, we'll discontinue them.
  
  – Pablo Escobar
  Mar 24 at 13:04
  

  
  
  
  

add a comment | 

2

firebaser here

There is no documented limit to the number of databases (often referred to as shards) you can have within a project. Each database essentially functions as a completely separate instance, so there isn't any reason to have a limit at all. As long as you can spread your users over the shards, it can scale infinitely.

That said: Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. You might be able to get by with much fewer shards.

But if you really need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.

share|improve this answer

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you so much @Frank van Puffelen, the fact that each database instance function separately is relaxing. Currently, we have created 20 db instances. Actually we want to stop using the previous db instances, as some developers are misusing those databases' data for their apps, the database structured is exposed and we can't put any kind of authentication for our apps' old version to run properly. So we planned when most the users will have moved to the new dbs, we'll discontinue them.
  
  – Pablo Escobar
  Mar 24 at 13:04
  

  
  
  
  

add a comment | 

firebaser here

There is no documented limit to the number of databases (often referred to as shards) you can have within a project. Each database essentially functions as a completely separate instance, so there isn't any reason to have a limit at all. As long as you can spread your users over the shards, it can scale infinitely.

That said: Be sure to check your Firebase console for the number of concurrently active users on each shard, as DAU hardly ever translates 1:1 to concurrency. You might be able to get by with much fewer shards.

But if you really need that many instances after that check, 20 is not an unreasonable number. If you experience any issues or grow further and want a double-check, I'd reach out to Firebase support for personalized help.

share|improve this answer

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

share|improve this answer

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428

answered Mar 23 at 14:14

Frank van PuffelenFrank van Puffelen

251k31401428