Firebase database strategy for 100k + concurrent connections?
If you are going to implement a firebase backend service that goes insanely viral and has a growth rate of over 40% in 10 days and you hit the flame plan quota with nothing more than 100,000 concurrent connections. What working strategies can be implemented with firebase to handle concurrent connections over 100k? 1M? 100M? 1B !!?
source to share
100k concurrents - quite a lot of concurrent connections, but it is possible for large applications as well, since we had s> 1MM applications.
In general, the strategy for this is to penalize data across multiple databases. It is rather trivial if the data is all independent (for example, for each todo todo list), since you can assign a developer to the database and never sync with the databases.
Read-only data (like 1: N chat) is usually also pretty easy as you can do the same "allow anyone to connect to any of N copies of the same database" and have one user / job update all they have the same information.
For more complex schemes (in particular 1: 1 chat) that allow developers to connect to any database, it might be advisable to synchronize data between databases using Cloud Function or another system.
If you expect to realistically reach 100k + concurrents, feel free to contact our support team with more usage information and we'll be happy to work with you.
source to share