Chapter 78. Treat Your Infrastructure like Software
Zachary Nickens
Infrastructure is important. Infrastructure and application code are equally critical to success as a cloud engineer. Most engineers either choose the correct runtime environment, or iterate through runtime environments until they find the appropriate one for their application. How you provision, deploy, and recover whatever infrastructure you use is critical to choosing the appropriate runtime. Most cloud engineers love designing, architecting, developing, and deploying applications. Error reporting, debugging, logging and log aggregation, and alerting generally are easily baked in when working on a major cloud platform or working with common toolsets.
One of the greatest advantages to working in the cloud is the plethora of managed services and tools readily available to meet those challenges. Cloud is awesome! That’s a knife that cuts both ways, however. Managed services that are easily turned on can be easily and accidentally turned off. A managed database or a function running on serverless compute can be inadvertently dropped. And if you are provisioning and deploying those resources by hand or via shell scripts, they can introduce unnecessary toil into your downtime recovery and remediation strategies. And nobody wants toil.
Using managed services is a great strategy. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access