First, some background: I'm a heavy Django user. Django has settings that are loaded once at runtime and usually they're in version control (they're committed to the repo). That means that, if you want to change a value to a setting, you must commit to the repo and re-deploy. If you're using Kubernetes, this might take several minutes (re build the images, upload to the registry, replicate on all the pods, etc).
That'd be the advantage of this solution. Imagine you have to change a setting IMMEDIATELY (something bad happen). You must: * commit to the repo and push * wait for CI (tests, formatting, protocols of PR approvals in a team, etc) * wait for CD (build image, push to registry, replicate, etc) It can potentially take several minutes.
Now, the major drawbacks I see with this service are: * Security: do you guys feel confident/strong enough to store important data of the app? Go so far as hosting secrets for example? (We use the Secret Manager in AWS). * Latency: in our case we read confs only once when the WSGI server starts. Can you be fast enough? * Availability: if your site goes down, my app goes down. Can you ensure 99.9999 availability?
Anyways, this is definitively a needed service. It does have its challenges, but you guys are onto something for sure. Congrats!