Revision as of 11:43, 30 January 2016 edit Andy Dingley (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers 163,319 edits MOS caps in headings ← Previous edit		Revision as of 11:45, 30 January 2016 edit undo Andy Dingley (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers 163,319 edits →Overview: links Next edit →
Line 6: ==Overview== IaC grew as a response to the difficulty posed from two pieces of disruptive technology – utility computing and second-generation web framework. This brought about widespread scaling problems for many enterprises that were previously only witnessed by huge companies.<ref name="CCA" >{{cite report IaC grew as a response to the difficulty posed from two pieces of disruptive technology – utility computing and second-generation web framework. This brought about widespread scaling problems for many enterprises that were previously only witnessed by huge companies.<ref name= CCA>{{cite report \|last= Fletcher \| first= Colin \| last2= Cosgrove \| first2=Terrence \|title=Innovation Insight for Continuous Configuration Automation Tools\|website=Gartner\|url=http://www.gartner.com/document/3119319?ref=unauthreader \| date=26 August 2015}}</ref> In 2006 specifically, new challenges were brought to the forefront that shook the technology industry; the launch of Amazon web services’ Elastic Compute Cloud and the 1.0 version of [[Ruby on Rails]] just months before.<ref>{{cite journal \| last=Bower \|first=Joseph L. \| last2= Christensen \| first2= Claton M. \| title= Disruptive Technologies: Catching the Wave \| journal= Harvard Business Review}}</ref> With new tools emerging to handle this every growing field, the idea of Infrastructure as Code was born. The thought of modeling infrastructure with code, and then having the ability to design, implement, and deploy applications infrastructure with known software best practices appealed to software developers and IT infrastructure administrators. The ability to treat it like code and use the same tools as any other software project would allow developers to rapidly deploy applications.<ref>{{cite journal \| last= Riley\| first= Chris\| date= 12 November 2015 \| title= Version Your Infrastructure\| url= http://devops.com/2015/11/12/version-your-infrastructure/ \| journal=DevOps.com}}</ref> \|last= Fletcher \| first= Colin \| last2= Cosgrove \| first2=Terrence \|title=Innovation Insight for Continuous Configuration Automation Tools \|website=Gartner \|url=http://www.gartner.com/document/3119319?ref=unauthreader \| date=26 August 2015 }}</ref> In 2006 specifically, new challenges were brought to the forefront that shook the technology industry; the launch of [[Amazon Web Services]]’ [[Elastic Compute Cloud]] and the 1.0 version of [[Ruby on Rails]] just months before.<ref >{{cite journal \| last=Bower \|first=Joseph L. \| last2= Christensen \| first2= Claton M. \| title= Disruptive Technologies: Catching the Wave \| journal= [[Harvard Business Review]] }}</ref> With new tools emerging to handle this every growing field, the idea of Infrastructure as Code was born. The thought of modelling infrastructure with code, and then having the ability to design, implement, and deploy applications infrastructure with known software best practices appealed to software developers and IT infrastructure administrators. The ability to treat it like code and use the same tools as any other software project would allow developers to rapidly deploy applications.<ref >{{cite journal \| last= Riley\| first= Chris\| date= 12 November 2015 \| title= Version Your Infrastructure \| url= http://devops.com/2015/11/12/version-your-infrastructure/ \| journal=DevOps.com }}</ref> ==Added value and advantages==

Infrastructure as code: Difference between revisions