Infrastructure as Code, 3rd Edition

Chapter 5. Design Principles For Infrastructure as Code

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 5th 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].

A good system architecture leads to an implementation that is effective in meeting the needs of its users, and that is easy to continuously evolve with those needs. This chapter discusses how to do this in the context of infrastructure implemented through code.

Traditional approaches to infrastructure architecture assume that an initial design, once implemented, won’t change much. Many people aspire to treat designing software like designing a bridge or a building.¹ These designers try to anticipate all potential future needs and then design a system that can handle them all. The result is most often overly complex systems that need to be completely replaced a few years later.

Software, including infrastructure defined as code, is much easier to change than a bridge or skyscraper. The difficulties that people have encountered with changing software mostly come from complex ...