Source: Infrastructure as Code (Kief Morris)
"Infrastructure as code" is the idea of creating/managing infrastructure declaratively using code. Writing it in code has many benefits, which we will describe below. Like many powerful ideas in software development, it consists of a set of principles, practices and tools.
Here are some good reading materials to help you understand this concept:
Challenges with Dynamic Infrastructure
- Server Sprawl
- Configuration Drift
- Snowflake Servers
- Fragile Infrastructure
- Automation Fear
- Erosion
- Systems Can Be Easily Reproduced
- Systems Are Disposable
- Systems Are Consistent
- Processes Are Repeatable
- Design Is Always Changing
- Use Definition Files
- Self-Documented Systems and Processes
- Version Control All the Things (Avoid using GUIs more than once)
- What to version control? Database schemas, web server configuration files, application server configuration information, message queue configuration, and every other aspect of the system that needs to be changed for your system to work should be under version control.
- Continuously Test Systems and Processes
- Small Changes Rather Than Batches
- Keep Services Available Continuously
- What is it?
- What are its requirements?
- Programmable
- On-Demand
- Self-Service
- Infrastructure Resources Provided by the Platform
- Compute Resources
- Storage Resources
- Network Resources
- Requirements:
- Scriptable Interface
- Unattended Mode for Command-Line Tools
- Support for Unattended Execution
- Externalized Configuration
- Working with Infrastructure Definition Tools
- Provisioning Infrastructure with Procedural Scripts
- Defining Infrastructure Declaratively
- Using Infrastructure Definition Tools