Build Configuration — Cloud Native Way

Cloud native configs for applicaitons need to go beyond centralised config repository. Ideal situation can be to accomadate multiple config sources in a incremental fashion.

Builder design pattern comes to the rescue here. It enables creation of configs based on multiple config source’s specified(config sources can be both centralised or local). For example config source1: has 10 key/values , source2: has 12 key/values. Builder can be used to build a composite config with 22 keys from the varied sources.

In the Microsoft world this can be acheived with the config builder — https://docs.microsoft.com/en-us/aspnet/config-builder

In the above diagrem the key’s in Azure app configuration are from the central config and available to all app config’s. The key’s in Appservice configuration are available specific to the application.