Infrastructure as code: Difference between revisions

Revision as of 11:18, 15 August 2016

Revision as of 19:57, 26 August 2016

Line 38:

==Types of approaches ==

There are generally twothree approaches to IaC: [[declarative programming|declarative]] (functional) vs. [[imperative programming|imperative]] (procedural) vs. intelligent (environment aware). The difference between the declarative, andthe imperative and the intelligent approach is essentially '' 'what' '' versus '' 'how' '' versus 'why' . {{anchor|Declarative}}The declarative approach focuses on what the eventual target configuration should be; whereas,the {{anchor|Imperative}}imperative focuses on how the infrastructure is to be changed to meet this and the intelligent focuses on why the configuration should be a certain way in consideration of all the co-relationships and co-dependencies of multiple applications running on the same infrastructure typically found in production.<ref >{{cite web

| url= https://www.scriptrock.com/blog/articles/declarative-vs.-imperative-models-for-configuration-management

| title= Declarative v. Imperative Models for Configuration Management: Which Is Really Better?

|website= Scriptrock.com

| access-date= 14 December 2015

}}</ref> The declarative approach defines the desired state and the system executes what needs to happen to achieve that desired state. Imperative defines specific commands that need to be executed in the appropriate order to end with the desired conclusion. The intelligent determines the correct desired state before the system executes what needs to happen to achieve that desired state. Environment aware desired state is the next generation of IaC. <ref >{{cite magazine

|last= Loschwitz | first= Martin

| date= 14 November 2014