Chapter 7. Automating at Enterprise Scale
In the first half of this book, you learned how to develop modules in a maintainable, scalable, and efficient way. You reviewed several common and emergent practices, including step-by-step walkthroughs of how to proceed, and you evaluated scenarios where they’re effective—or not. You recognize that even the best of practices have limitations or diminishing returns, and that documenting and developing policies around deviations and nuances is imperative. If your organization is sufficiently small (or if your specific purview is only a portion of the organization’s overall infrastructure/platform ecosystem), you may have most of the tools you need to achieve your goals and expectations—in which case, you may be able to skip ahead to Chapter 10, which presents various validation, troubleshooting, and remediation techniques, until you’re ready to expand the ecosystem (or your responsibility) beyond a single project. However, most TF practitioners do operate within a large organization, and even if you’re presently not responsible for other portions of the ecosystem, it’s valuable to see how the ecosystem as a whole fits together.
In this chapter, and for most of the remainder of the book, we’ll shift our focus beyond individual projects and how they manifest more or less in isolation up to module compositions, to the interactions, boundaries, and dependencies—which may be explicit and fully automated, or implicit and largely manually procedural—of ...
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