book

Infrastructure as Code, Patterns and Practices

Name: Infrastructure as Code, Patterns and Practices
Author: Rosemary Wang
ISBN: 9781617298295

by Rosemary Wang

August 2022

Intermediate to advanced

400 pages

12h 4m

English

Manning Publications

Audiobook available

Read now

Unlock full access

inside front cover
Infrastructure as Code, Patterns and Practices
Copyright
contents
front matter
prefaceacknowledgmentsabout this bookWho should read this book?How this book is organized: A roadmapAbout the codeliveBook discussion forumAbout the cloud providerOther online resourcesabout the authorabout the cover illustration
Part 1. First steps
1 Introducing infrastructure as code
1.1 What is infrastructure?1.2 What is infrastructure as code?1.2.1 Manual configuration of infrastructure1.2.2 Infrastructure as code1.2.3 What is not infrastructure as code?1.3 Principles of infrastructure as code1.3.1 Reproducibility1.3.2 Idempotency1.3.3 Composability1.3.4 Evolvability1.3.5 Applying the principles1.4 Why use infrastructure as code?1.4.1 Change management1.4.2 Return on time investment1.4.3 Knowledge sharing1.4.4 Security1.5 Tools1.5.1 Examples in this book1.5.2 Provisioning1.5.3 Configuration management1.5.4 Image buildingSummary
2 Writing infrastructure as code
2.1 Expressing infrastructure change2.2 Understanding immutability2.2.1 Remediating out-of-band changes2.2.2 Migrating to infrastructure as code2.3 Writing clean infrastructure as code2.3.1 Version control communicates context2.3.2 Linting and formatting2.3.3 Naming resources2.3.4 Variables and constants2.3.5 Parametrize dependencies2.3.6 Keeping it a secretSummary
3 Patterns for infrastructure modules
3.1 Singleton3.2 Composite3.3 Factory3.4 Prototype3.5 Builder3.6 Choosing a patternSummary
4 Patterns for infrastructure dependencies
4.1 Unidirectional relationships4.2 Dependency injection4.2.1 Inversion of control4.2.2 Dependency inversion4.2.3 Applying dependency injection4.3 Facade4.4 Adapter4.5 Mediator4.6 Choosing a patternSummary

Part 2. Scaling with your team
5 Structuring and sharing modules
5.1 Repository structure5.1.1 Single repository5.1.2 Multiple repositories5.1.3 Choosing a repository structure5.2 Versioning5.3 Releasing5.4 Sharing modulesSummary
6 Testing
6.1 The infrastructure testing cycle6.1.1 Static analysis6.1.2 Dynamic analysis6.1.3 Infrastructure testing environments6.2 Unit tests6.2.1 Testing infrastructure configuration6.2.2 Testing domain-specific languages6.2.3 When should you write unit tests?6.3 Contract tests6.4 Integration tests6.4.1 Testing modules6.4.2 Testing configuration for environments6.4.3 Testing challenges6.5 End-to-end tests6.6 Other tests6.7 Choosing tests6.7.1 Module-testing strategy6.7.2 Configuration testing strategy6.7.3 Identifying useful testsSummary
7 Continuous delivery and branching models
7.1 Delivering changes to production7.1.1 Continuous integration7.1.2 Continuous delivery7.1.3 Continuous deployment7.1.4 Choosing a delivery approach7.1.5 Modules7.2 Branching models7.2.1 Feature-based development7.2.2 Trunk-based development7.2.3 Choosing a branching model7.3 Peer review7.4 GitOpsSummary
8 Security and compliance
8.1 Managing access and secrets8.1.1 Principle of least privilege8.1.2 Protecting secrets in configuration8.2 Tagging infrastructure8.3 Policy as code8.3.1 Policy engines and standards8.3.2 Security tests8.3.3 Policy tests8.3.4 Practices and patternsSummary
Part 3. Managing production complexity
9 Making changes
9.1 Pre-change practices9.1.1 Following a checklist9.1.2 Adding reliability9.2 Blue-green deployment9.2.1 Deploying the green infrastructure9.2.2 Deploying high-level dependencies to the green infrastructure9.2.3 Using a canary deployment to the green infrastructure9.2.4 Performing regression testing9.2.5 Deleting the blue infrastructure9.2.6 Additional considerations9.3 Stateful infrastructure9.3.1 Blue-green deployment9.3.2 Update delivery pipeline9.3.3 Canary deploymentSummary
10 Refactoring
10.1 Minimizing the refactoring impact10.1.1 Reduce blast radius with rolling updates10.1.2 Stage refactoring with feature flags10.2 Breaking down monoliths10.2.1 Refactor high-level resources10.2.2 Refactor resources with dependencies10.2.3 Repeat refactoring workflowSummary
11 Fixing failures
11.1 Restoring functionality11.1.1 Rolling forward to revert changes11.1.2 Rolling forward for new changes11.2 Troubleshooting11.2.1 Check for drift11.2.2 Check for dependencies11.2.3 Check for differences in environments11.3 Fixing11.3.1 Reconcile drift11.3.2 Reconcile differences in environments11.3.3 Implement the original changeSummary
12 Cost of cloud computing
12.1 Manage cost drivers12.1.1 Implement tests to control cost12.1.2 Automate cost estimation12.2 Reduce cloud waste12.2.1 Stop untagged or unused resources12.2.2 Start and stop resources on a schedule12.2.3 Choose the correct resource type and size12.2.4 Enable autoscaling12.2.5 Set a resource expiration tag12.3 Optimize cost12.3.1 Build environments on demand12.3.2 Use multiple clouds12.3.3 Assess data transfer between regions and clouds12.3.4 Test in productionSummary
13 Managing tools
13.1 Using open source tools and modules13.1.1 Functionality13.1.2 Security13.1.3 Life cycle13.2 Upgrading tools13.2.1 Pre-upgrade checklist13.2.2 Backward compatibility13.2.3 Breaking changes in upgrades13.3 Replacing tools13.3.1 New tool supports import13.3.2 No import capability13.4 Event-driven IaCSummary
Appendix A. Running examples
A.1 Cloud providersA.1.1 Google Cloud PlatformA.1.2 Amazon Web ServicesA.1.3 Microsoft AzureA.2 PythonA.2.1 Install Python librariesA.2.2 Run PythonA.3 HashiCorp TerraformA.3.1 JSON configuration syntaxA.3.2 Initialize stateA.3.3 Set credentials in your terminalA.3.4 Apply TerraformA.3.5 Clean up
Appendix B. Solutions to exercises
index
inside back cover

Content preview from Infrastructure as Code, Patterns and Practices

7 Continuous delivery and branching models

This chapter covers

Designing delivery pipelines to avoid pushing failures to production systems
Choosing a branching model for infrastructure configuration for team collaboration
Reviewing and managing changes to infrastructure resources within your team

In the previous chapters, you learned how to write patterns for modules and dependencies. You also applied some general practices for writing infrastructure as code and sharing modules. The patterns, practices, and workflows had a lot of steps.

Furthermore, many of the workflows require careful coordination of changes. One day, you might try to make a change only to find out that your teammate’s updates might overwrite yours! How do you make sure ...

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

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781617298295Publisher Support Publisher Website

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Infrastructure as Code, Patterns and Practices

by Rosemary Wang

7 Continuous delivery and branching models

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.