NEXTGEN DEVOPS — Enterprise IT Before 2000: 1.1 Introduction: Why Study What Came Before 1 1.2 What "Enterprise IT" Means 3 1.3 A Periodization of Enterprise Computing, 1950–2000 3 1.4 The Centralized Paradigm: Mainframe Computing 4 1.4.1 What a Mainframe Is 4 1.4.2 Architecture 5 1.4.3 The Technol

The Foundations of Modern Enterprise Computing

Learning Objectives

By the end of this chapter, you will be able to:

1. Define enterprise IT in terms of its four constituent dimensions — people, process, technology, and data — and explain why technology alone an insufficient definition is.
2. Describe the major phases of enterprise computing between 1950 and 2000 and identify the business pressures that drove each transition.
3. Explain the architecture of centralized mainframe computing, including its core technology stack and the operational culture built around it.
4. Analyze the client-server model: what problems it solved, what new problems it introduced, and why those new problems mattered.
5. Evaluate the pre-2000 operating model — sequential delivery, functional specialization, manual release execution, infrastructure-centric monitoring, and perimeter security — as a coherent system rather than a list of shortcomings.
6. Map specific pre-2000 practices to their modern equivalents in DevOps, cloud engineering, SRE, and DevSecOps, distinguishing genuine continuities from superficial resemblances.
7. Justify which historical controls an organization should preserve when modernizing, and which should be replaced by automation.