Infrastructure Concepts

External

• http://www.infrastructures.org
• Infrastructure as Code: Dynamic Systems for the Cloud Age by Kief Morris

Internal

• Infrastructure as Code
• Infrastructure as Code Concepts

Overview

In a cloud environment, infrastructure, as viewed by the user, is no longer represented by hardware, but by virtual constructs like servers, subnets and block devices. The hardware still exists, but infrastructure elements accessible to users "float" across it, can be manipulated by the infrastructure platform APIs and can be created, duplicated, changed and destroyed at will. They are referred to as infrastructure resources. Infrastructure resources can be instantiated, changed and destroyed by infrastructure as code to provide the infrastructure foundation for application runtimes and applications.

Application

Applications and services provide domain-specific capabilities to organizations and users. Everything in the underlying layers (application runtime, infrastructure platform) exists to enable this layer. Examples.

Application Runtime

The application runtime layer provides services and capabilities to the application layer. An application runtime is laid upon the infrastructure platform layer and it is assembled from infrastructure resources. The application runtime instance may include servers, clusters and serverless execution environments.

Infrastructure Platform

Infrastructure Resources

A cloud infrastructure platform abstracts infrastructure resources (compute, network, storage) from physical hardware. Infrastructure resources are assembled to provide application runtime instances.

Infrastructure Stack

• Stack integration point.

Cloud

NIST definition: https://www.nist.gov/programs-projects/nist-cloud-computing-program-nccp

Cluster

Cluster as code.

Configuration Drift

Configuration drift is variation that happens over time across systems that were once identical. Manually making changes in configuration (performance optimizations, permissions, fixes), even if the base was laid down by automation, causes configuration drift. Selectively using automation on some of the initially identical systems, but not on others, also causes configuration drift. This is how snowflake systems come into existence. Also see Minimize Variation. Once manually-introduced configuration drift occurs, the trust in automation goes down, because people are not sure how an automation will modify a manually-changed system. Interestingly, manual configuration creeps in because the automation is not run frequently and consistently, leading to a vicious circle. To avoid this spiral, make everything reproducible automatically and consistently run automation. Operational automation combined with good monitoring exposes configuration drift.

Governance

Lightweight Architectural Governance

Lightweight architectural governance aims to balance autonomy and centralized control. More in EDGE: Value-Driven Digital Transformation by Jim Robert Highsmith, Linda Luu, David Robinson and the The Goldilocks zone of lightweight architectural governance Jonny LeRoy talk.

Organizatorium

• Integration points