About Firebase Remote Configuration limitations

Question

We'll start to new project using the Firebase.

First of all, I'll try to set static like app version) to remote config to check the lower version in app-side.

So, I'd try to search the limitation/quota of the 'firebase remote configuration' such as traffic, connections, concurrent connections per month and so on, but I can't find any documents about Firebase remote configurations.

Can anybody help me?

Ergot

Possible duplicate of How is the Firebase Remote Config rate limit counted? – Bulley

Possibly helpful links: firebase.google.com/docs/remote-config/#policies_and_limits, firebase.google.com/docs/remote-config/… – Bulley

Is there any other limitations about traffic or concurrent connections ? above documents are limitations about the number of parameters and length of parameter. – Ergot

I've actually searched for something like that (specifically in the Pricings page), but there isn't anything explicitly mentioned in the documentations. – Bulley

#41098186 – Nina

Answer 1

There aren't really any official public numbers, partly because the team reserves the right to change them in the future to better suit the needs of the service.

That said, Remote Config is designed to be free for your apps, no matter how popular they become. You shouldn't ever have to worry about concurrent connections or connections per month or anything like that, as long as your client behaves reasonably.

What does that mean? Well, personally, my recommendation would be to not set your cache for anything less than 3 hours. If you need something faster than that, then you should really start looking into the Realtime Database. Otherwise, you should be find with Remote Config.

Violate