Where to keep Configurations?

whether it’s frontend configuration or backend configuration for the production environment, the question is where to keep them such that you don’t have to do deployments on config changes and also the system is controlled externally without much of a issue. This question is more relevant when you are building a SaaS platform, also this has become the best practice to do when you want to scale your application easily and fast.

What’s the solution?

Setup a low latency, highly cached API CRUD endpoint for the configuration which is used by the backend and the front-end. For high security you can use RSA encryption and decryption for the same and keep a separate copy for backend and frontend since few secrets are only kept on the backend only.

This will help the operations team also to control the application configuration without the intervention of the dev team, helps decoupling the responsibility and allows developer to focus on his sprint tasks better as he is no more concerned about the configurations after his first deployment for the newest configuration he has added.