Cloud Computing: 2012 Edition
Facing the Reality
Read the 2012 edition online as a historical work about the rise of cloud computing. This edition is for context, research, and continuity of ideas; the current book home with purchase links remains available separately.
A historical edition, not a current technical manual
Cloud Computing: Facing the Reality was originally published in 2012, when many organizations were still learning what cloud computing meant for infrastructure, software delivery, cost, governance, and business models.
This online edition keeps that text accessible for readers who want to understand the period. It is not presented as a current cloud architecture manual, vendor guide, procurement checklist, or security playbook.
A useful record for several kinds of readers
Use it to study how cloud vocabulary, adoption arguments, and early industry assumptions were framed in the early 2010s.
Read it for the enduring shift from ownership to access, and for the business-model logic behind service-based computing.
Compare the original cloud concerns with today's platform, DevOps, security, data, AI, and FinOps practices.
Use it to trace how questions of trust, governance, public services, and organizational readiness have persisted.
How to read this edition today
- Students and researchers can use this edition to study the vocabulary, assumptions, and business concerns that shaped early cloud adoption.
- Founders, CTOs, architects, and product leaders can read it as a reminder of the economic shift from owned infrastructure to managed capability.
- Institutional and public-sector readers can compare the 2012 concerns around trust, governance, access, and adoption with the cloud governance questions they face today.
- Vendor names, market claims, screenshots, pricing assumptions, and service examples should be treated as period evidence rather than current recommendations.
- For current buying information and commercial availability, use the book home page rather than this historical online edition.
What remains valid
- Cloud computing changed computing from asset ownership toward service access.
- The economic argument around elasticity, shared infrastructure, and operational leverage remains central.
- Cloud adoption is as much an organizational and business-model decision as a technical one.
- Trust, governance, data ownership, availability, and vendor dependence remain important design questions.
- Cloud lowered the entry barrier for small teams, institutions, public services, and new digital businesses.
What has changed since 2012
- Cloud is no longer novel; it is the default operating substrate for much of modern software.
- The platform stack has shifted through containers, Kubernetes, serverless, managed data platforms, edge services, and AI infrastructure.
- Security has moved from generic concern to specialized disciplines: cloud posture management, identity-first security, zero trust, supply-chain security, and compliance automation.
- Cost management has become a formal practice through FinOps, unit economics, committed usage, and workload optimization.
- AI, data residency, sovereignty, sustainability, and sector regulation now shape infrastructure decisions in ways that were less mature in 2012.
Notes for reading in 2026
Why this edition is online
This edition is made available for readers who want to understand how cloud computing was explained when the term was still moving from industry promise to everyday infrastructure.
The 2012 context
The book was written when SaaS, infrastructure services, and hosted platforms were becoming credible choices, but many organizations were still weighing trust, cost, data control, and operational readiness.
The durable argument
The central shift from owning technology assets to accessing managed capabilities remains important. The language has changed, but the economic and organizational logic still matters.
What has changed since 2012
Cloud is now ordinary infrastructure for much of software. Containers, Kubernetes, serverless platforms, DevOps, edge systems, AI infrastructure, security practice, regulation, and FinOps have changed the operating model.
How to use the original chapters
Read the chapters as a historical record of cloud adoption thinking. They are useful for concepts, vocabulary, and the evolution of concerns, but not for current procurement, architecture, compliance, or operations decisions.
Continuity with later work
Many themes in the book continue into later work on SaaS, platform architecture, DevSecOps, AI systems, and institutional computing maturity: technology matters most when it changes how organizations act.