Infrastructure as Code Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 18: Line 18:
==<span id='Small_Pieces'></span>Build Small, Simple, Loosely Coupled Pieces that Can Be Changed Independently==
==<span id='Small_Pieces'></span>Build Small, Simple, Loosely Coupled Pieces that Can Be Changed Independently==


[[Microservices]] fall into this category.
[[Microservices#Overview|Microservices]] fall into this category.


=Stack=
=Stack=

Revision as of 21:52, 29 December 2021

External

Internal

Overview

Infrastructure is not something you build and forget, in requires constant change: fixing, updating and improving. Infrastructure as Code is a set of technology and engineering practices aimed at delivering change more frequently, quickly and reliably, while improving the overall quality of the system at the same time. Trading speed for quality is a false dichotomy. Used correctly, Infrastructure as Code embeds speed, 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, it can benefit from lessons learned in software design patterns, principles and techniques such as test driven development, continuous integration, continuous delivery or refactoring.

Continuously Test and Deliver

Continuously testing small pieces encourages a modular, loosely coupled design.

Build Small, Simple, Loosely Coupled Pieces that Can Be Changed Independently

Microservices fall into this category.

Stack

Collection of infrastructure resources provisioned from cloud platforms.

Stack Instance