Infrastructure as code: Difference between revisions

Revision as of 11:53, 30 January 2016

Revision as of 11:55, 30 January 2016

Line 38:

==Types of approaches ==

There are generally two approaches to IaC [[declarative programming|declarative]] (functional) vs. [[imperative programming|imperative]] (procedural). The difference between the declarative and imperative approach is essential ''what'' versus ''how''. The declarative approach focuses on what the configuration should be; whereas, imperative focuses on how the infrastructure is to be configured.<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.<ref >{{cite magazine
|last= Loschwitz | first= Martin
| date= 14 November 2014
| title= Choosing between the leading open source configuration managers
| url=http://www.admin-magazine.com/Archive/2014/23/Choosing-between-the-leading-open-source-configuration-managers | magazine= Admin Network & Security | ___location= Lawrence, KS USA | publisher= Linux New Media USA LLC }}</ref>

| magazine= Admin Network & Security

| ___location= Lawrence, KS USA | publisher= Linux New Media USA LLC

}}</ref>

==Methods==