Infrastructure as Code Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
Continuously testing [[#Small_Pieces|small pieces]] encourages a modular, loosely coupled design. | Continuously testing [[#Small_Pieces|small pieces]] encourages a modular, loosely coupled design. | ||
==Build Small, Simple Pieces that Can Be Changed Independently== | ==<span id='Small_Pieces'></span>Build Small, Simple Pieces that Can Be Changed Independently== | ||
=Stack= | =Stack= |
Revision as of 00:50, 27 December 2021
Internal
Overview
Infrastructure is not something you build and forget, in requires constant change: fixing, updating and improving. Infrastructure as Code principles and tools help delivering change more frequently, quickly and reliably, while improving the overall quality of the system at the same time. Used correctly, Infrastructure as Code embeds quality, reliability and compliance into the process of making changes. Changing infrastructure becomes safer.
Core Practices
Define Everything as Code
Code can be versioned and compared.
Continuously Test and Deliver
Continuously testing small pieces encourages a modular, loosely coupled design.
Build Small, Simple Pieces that Can Be Changed Independently
Stack
Collection of infrastructure resources provisioned from cloud platforms.