When the infrastructure was physical, we couldn't rebuild servers on a whim. It required a lot of work! Now that the infrastructure is treated as code, components in the infrastructure can be treated as objects. As such, due to the speed at which we can make changes, we can now treat infrastructure components as disposable.
Once you nail down this concept, your infrastructure will gain the predictability and standardization necessary to navigate constant change. Being able to manage the constant flux of enterprise architecture is vital. But trying to control each and every little change is maddening. To be sure that any given server is in the state you need, you can simply blow it away and create another. Since your entire infrastructure is defined in code, all the instructions to do so are stored in source control. Rebuilding a server in PowerShell could simply be a matter of Get-Server | Remove-Server –PassThru | New-Server. All the logic and instructions to make this happen already exist.
Devops done right
Operations needs to evolve to stay relevant. The industry is continuing to be more software-centric. Everything is a service now, and many businesses are choosing the cloud over traditional on-premises solutions. To keep up, we must embrace our inner developers and treat our infrastructure as software and manage it as such. We must manage our servers as cattle -- anonymous creatures only on this earth to provide us sustenance rather than pets with names and custom collars. This takes code and new tools based on our ability to write scripts to make the most of them.
In previous years, it was not possible for developers and operations to work side by side. Now that we're able to represent traditionally physical components as software, operations can stand on common ground as developers through code. But doing so will take a developer’s-eye view of your traditional administration tasks.
Sign up for CIO Asia eNewsletters.