Infrastructure as Code, 3rd Edition

Chapter 6. Infrastructure Components

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles. This will be the 6th chapter of the final book. Please note that the GitHub repo will be made active later on. If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

TODO

Consider examples to make these component concepts more clear, especially in terms of specific tools?

A key part of system design is grouping elements and defining relationships between those groups. We define these groupings as architectural units, or components, that we can use in diagrams and discussions. Some common components for software design include applications, microservices, libraries, and classes, which span different levels of a system. This chapter will describe components that we can use to discuss system designs with Infrastructure as Code.

Our industry does not have widely agreed definitions of what components are relevant for Infrastructure as Code, or what to call them. So for the purposes of this book, I’ve defined four types of components. These components are IaaS resources, code libraries, deployable infrastructure stacks (“stacks” for short), and infrastructure ...