DeploymentDeploying a change to a platform that is currently running on 400 production servers.
MonitoringMonitoring user experience such as response times across a cloud platform where users are connecting to different machines in different data centers.
Configuration ManagementKeeping an accurate history of configurations across complex environments.
RollbackReverting a large number of servers back to a historical configuration.systems and applications sponsored by different business units.
AdministrationAutomating cumbersome administrative tasks such as daily backups across a large number of devices.
AlertsGenerating and handling alerts. For example, a large telecom company might receive thousands of alerts every few minutes and they need to automatically figure out which indicate a problem that actually impacts customers or end-users.
ProvisioningA data center needs to quickly change the linux version on 50 physical machines to meet customer demand.
CapacityAn internet service needs to balance load across 7 data centers.
ResilienceA cloud service has an average of 7 servers fail in various ways each day. This needs to be immediately detected and handled by redirecting load to working servers.
|Overview: Infrastructure As Code|
In the past, infrastructure teams were mostly specialists in hardware and operating systems who focused on connecting and configuring things. Infrastructure as code represents a shift towards having infrastructure managed by developers.