Building Evolutionary Architectures

Configure Some of the Things All of the Time

PenultimateWidgets has been burned in the past by having hard-coded constants in several places in their code base, governing both business cases (thresholds, maximums, etc.) and operational concerns. Architects need a way to prevent developers from accidentally hard-coding critical values.

• Categories: atomic, triggered
• Requirements:
• architects define a list of dynamic values that should always pulled from a configuration file, not hard coded.
• Additional Context:
• all the teams use deployment pipelines and a declarative language to provision infrastructure