All geek questions in one place

Firebase Remote Config vs Database

I have some options that I want to control without updating. There are 2 options:

  • Remote configuration - select them with a default cache for 12 hours.
  • Database - creation of a configuration object and selection during application initialization.

If I use a remote configuration and change some parameter, a condition may arise that some of my users will have to wait 12 hours for the parameter change to take effect. Some of my parameters cannot be incorrect for such a long time. Does this mean that these parameters should be stored in the database configuration object, and the remote configuration only for parameters that are valid in order to remain invalid for 12 hours?

+5
source share
3 answers

At first glance, Firebase Remote Config looks like a simple set of key / value pairs that you pull into your application. If that's all you need, Remote Config will not offer you anything better than in the Realtime Database. But this is much more than if you read the list of functions from the link in the first sentence here.

What distinguishes Remote Config from the Realtime database is that you can set conditions for parameters to configure who sees what values.

, Remote Config Google Analytics Firebase, , , A/B Firebase Console. , , (, Firebase Realtime, ).

Firebase Realtime , . , - , , .

, Remote Config. API .

+8

- .

A/B. . "" !

BTW, firebaseRemoteConfig.fetch(<your_new_time_in_sec>) 10 (3600 )

!

https://firebase.google.com/docs/remote-config/ios#caching_and_throttling

https://firebase.google.com/docs/remote-config/android#caching

Firebase . .

+1

To complete the picture, the remote configuration now provides the ability to receive real-time updates using cloud functions.

https://firebase.google.com/docs/remote-config/propagate-updates-realtime

0
source

Source: https://habr.com/ru/post/1681073/

More articles:


All Articles