Vocabulary · Volume 1 and Volume 2
Obligation
What the organization has promised to pay, including promises that outlast the reason for making them. The contract, not current use, determines which kind of obligation exists and what can stop if the workload disappears.
Discussed in the book
Chapters where “Obligation” is discussed at length, ranked by how directly each section treats it.
- Volume I, Chapter 1: What Computing Costs
Sections: Several dimensions of the same dollar · Enough information to have the next conversation · A bill we can follow
- Volume I, Chapter 3: The Players and the Vocabulary
Sections: When agreement does not arrive
- Volume I, Chapter 10: Specialized Hardware
Sections: Acquiring it
- Volume I, Chapter 11: Exotic Hardware: Quantum and Emerging Capacity
- Volume I, Chapter 12: Databases and Data-Bound Technologies
Sections: Build a data-capacity decision record
- Volume I, Chapter 13: Measuring Value
- Volume II, Chapter 16: A Portfolio of Customers
Sections: When the plans do not agree
- Volume II, Chapter 18: Reserve Capacity
- Volume II, Chapter 21: Multiple Markets
Sections: Sovereignty in this context · Segmentation costs utilization · One register, not a private law firm
- Volume II, Chapter 22: The Monthly Capacity Review
Sections: When the meeting cannot agree
- Volume II, Chapter 23: What Scale Brings
Sections: The obligations grow their own management · How to read this chapter
- Volume II, Chapter 24: Markets for Compute
Related posts
Blog posts that discuss “Obligation”.