Somewhat related, how are other gophers handling dynamic configuration in their go apps? Such as if the app is tied to consul or vault to get some config value. How do you handle the propagation of config changes cleanly, especially if it impacts something "big" like your DB pool? Do you have mutexes everywhere you read from the config pointer you pass around?
I noodled on this a while ago and figured it was easier to just restart the app on config changes than try to change things on the fly =D
I noodled on this a while ago and figured it was easier to just restart the app on config changes than try to change things on the fly =D