Infrastructure.as.Code (IaC)

Define Everything as Code
Defining all your stuff “as code” is a core practice for making changes rapidly and
reliably. There are a few reasons why this helps:

• Re-usability

If you define a thing as code, you can create many instances of it. You can repair
and rebuild your things quickly, and other people can build identical instances of
the thing.

• Consistency

Things built from code are built the same way every time. This makes system
behavior predictable makes testing more reliable and enables continuous testing
and delivery.

• Transparency

Everyone can see how the thing is built by looking at the code. People can review
the code and suggest improvements. They can learn things to use in other codes,
gain insight to use when troubleshooting, and review and audit for compliance.