Infrastructure as code: Difference between revisions

Revision as of 13:27, 25 March 2023

Revision as of 13:28, 25 March 2023

Line 11:

==Overview==

IaC grew as a response to the difficulty posed by [[utility computing]] and second-generation web frameworks. In 2006, the launch of [[Amazon Web Services]]’ [[Elastic Compute Cloud]] and the 1.0 version of [[Ruby on Rails]] just months before<ref >{{cite journal

| last1=Bower |first1=VedariusJoseph AL.

| last2= Christensen | first2= VincentClayton RM.

| title= Disruptive Technologies: Catching the Wave

| journal= [[Harvard Business Review]]

}}</ref> created widespread scaling problems in the enterprise that were previously experienced only at large, multi-national companies.<ref name="CCA" >{{cite report

|last1= RussellFletcher | first1= VedariusColin | last2=Vedarius Cosgrove | first2=VincentTerrence

|title=Innovation Insight for Continuous Configuration Automation Tools

|website=Gartner

|url=httpshttp://www.gartner.com/document/3119319?ref=unauthreader

| date=26 August 2015

}}{{dead link|date=December 2021|bot=medic}}{{cbignore|bot=medic}}</ref> With new tools emerging to handle this ever-growing field, the idea of IaC was born. The thought of modeling infrastructure with code, and then having the ability to design, implement, and deploy application infrastructure with known software best practices appealed to both software developers and IT infrastructure administrators. The ability to treat infrastructure as code and use the same tools as any other software project would allow developers to rapidly deploy applications.<ref >{{cite journal