You need a way to get your code from source into staging and production. Each microservice has its own unique runtime configuration: its dependencies (e.g., databases, other services), its deployment requirements (e.g., auto scaling group configuration), and more. Centralized management of the runtime configuration of services creates high operational overhead and complexity. Instead, consider integrating runtime configuration directly with your microservices deployment.
We’re happy to help! Look for answers in the rest of the Microservices Architecture Guide, start using our open source Ambassador API Gateway, send us an email at email@example.com, or contact our sales team.