Dominik Pabst
e446a79090
|
2 years ago | |
---|---|---|
.. | ||
100-service-mesh | 2 years ago | |
102-configuration-management | 2 years ago | |
103-infrastructure-provisioning | 2 years ago | |
100-docker.md | 3 years ago | |
101-containers.md | 2 years ago | |
101-lxc.md | 3 years ago | |
104-docker-swarm.md | 2 years ago | |
104-kubernetes.md | 2 years ago | |
104-mesos.md | 3 years ago | |
104-nomad.md | 3 years ago | |
readme.md | 2 years ago |
readme.md
Infrastructure as Code
Sometimes referred to as IaC, this section refers to the techniques and tools used to define infrastructure, typically in a markup language like YAML or JSON. Infrastructure as code allows DevOps Engineers to use the same workflows used by software developers to version, roll back, and otherwise manage changes.
The term Infrastructure as Code encompasses everything from bootstrapping to configuration to orchestration, and it is considered a best practice in the industry to manage all infrastructure as code. This technique precipitated the explosion in system complexity seen in modern DevOps organizations.
Free Content What is Infrastructure as Code? What is Infrastructure as Code? Difference of Infrastructure as Code Tools GUIs, CLI, APIs: Learn Basic Terms of Infrastructure-as-Code Understanding Infrastructure as Code (IaC) in less than 10 minutes