Microservices: So, how do you guys deal with shared configurations across all your different services?
Natalia Vallejos
·3571 views
So, we're splitting up our big application into smaller microservices, and honestly, managing all the settings is starting to get messy. Things like database addresses, secret keys, and even those on-off switches for features are all over the place. We've checked out dedicated config tools, you know, like Spring Cloud Config or Consul. But I'm wondering what everyone else is up to. Are you guys using a main config service to keep everything in one spot, or do you like to just package the config right along with each service when you deploy it? What problems or benefits have you found with whichever way you chose?
38 comments