are impressive, easy to explain and the benefits are obvious. Infrastructure As Code (IaC), like dynamic hosting, also has tremendous potential. To understand the benefits of Infrastructure as Code, let's take a look at the traditional approach. Not only are the servers mostly static, but their setup and configuration require mainly manual steps.
For example, opening the box when a new server is delivered and connecting the cables is a manual task. Using Infrastructure as Code, however, allows these processes to run in a virtual environment. These steps as well as all further setup and configuration work can be written as code.
A big problem with the manual approach which may surprise management but is no secret to server administrators, is that infrastructure setup and changes are often insufficiently documented or not documented at all. In other words, ask a room full of server administrators about the installation and changes blog and see who meets your eye.
To be fair, documenting is time-consuming and server administrators are always under great pressure, especially when changes need to be made. However, in an emergency situation, proper documentation can be a lifesaver. Conversely, a change to the infrastructure without documentation to some extent is like driving in the dark with the headlights off.