Architecture as Code

Part II. Architecture and Engineering Practices

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 Part IV of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

Architects are frequently responsible for lots of tasks on software projects that aren’t directly related to software architecture (or so it seems). For example, they must frequently make choices about coding approaches (Test-Driven Development or solo coding?) and version-control strategies (mono-repo or repo-per-service?). While it would be convenient and nice to have a clean separation between these decisions and purely architectural ones, they are, like so many other architecture concerns, entangled.

We strive in this book to provide general definitions of our intersections, and this one is no different. However, we must first distinguish between software development processes and engineering practices.

In software development, the term process describes the practices, artifacts, rituals, and other activities that facilitate a group of people in building software. The history of software development is littered with processes that were invented, used ...