Free consultation
Chapter 7 / Configuration

Configuration
Management

Systems change over time. Make changes, capacity, and source code traceable, keeping a state that is easy to roll back later.

View configuration managementBack to contents
Diagram of configuration management
Make changes, capacity, and source traceable later.
Change / Capacity / Source

Record before changing, notice before growing

Change management records who changed what and when. Capacity management stays ahead by watching usage. Source control lets you reproduce the same state.

1
Change managementDecide request, approval, recording, and rollback.
2
Capacity managementMonitor usage and prepare before it grows.
3
Source controlVersion-control code and configuration to improve reproducibility.

Change management

  • Decided change recording and approval flow.
  • Decided how to check impact scope.
  • Prepared rollback procedures.

Capacity management

  • Decided usage monitoring items.
  • Decided criteria for scaling up/down.
  • Checking cost impact.

Source control

  • Version-controlling code.
  • Codifying configuration.
  • Can reproduce environments.

Three things to remember in the end

Decide with numbers, separate responsibility, and watch and fix. Returning to these three makes Azure design decisions easier.

SLA/RTO/RPOIaaS/PaaS/RBACMonitoring/Backup/Change
Get a free consultation