5.6: Detailed Captions - Chapter 5

Overview

• Chapter: 5 — Designing an Enterprise Cloud Strategy
• Total Figures Proposed: 8
• Figure Types Used: Architecture Diagram, Comparison Table, Flowchart, Conceptual Illustration, Infographic, Network Diagram

Figure 5.1.1

Title: Cloud Computing Ecosystem — Stakeholder Roles and Interactions

Detailed Caption: Three navy-headed stakeholder cards sit at the points of a triangular layout — Cloud Clients (top-left, with a monitor icon and "Client Dashboard"), Cloud Vendors (top-right, with a server-rack icon and "Vendor Dashboard"), and Cloud Partners (bottom-center, with a chart icon and "Partner Dashboard") — and each is linked by a teal bidirectional arrow to a central white panel labeled "Ecosystem Management Layer" that exposes three sub-pills: Onboarding, Coordination, and Marketplace. A wide warm-gold strip beneath the diagram reads "Service Layers: Provisioning | Subscription | Governance," signaling the cross-cutting capabilities the management layer provides to every stakeholder. By placing the management layer literally in the middle of the three actor groups, the figure communicates the chapter's central organizing claim — that a healthy cloud ecosystem is not a free-for-all but a hub-and-spoke arrangement where onboarding, coordination, and marketplace functions are deliberately centralized so clients, vendors, and partners can interoperate.

Figure 5.2.1

Title: The Seven Principles of Enterprise Cloud Architecture (CCOA)

Detailed Caption: Seven numbered hexagons orbit a central teal pill labeled "Enterprise Cloud Strategy," each connected to it by a thin warm-gold dashed line. Reading clockwise from the top, the hexagons display: 1 Integrated Ecosystem Mgmt (connected-nodes icon), 2 Virtualization (layered-squares icon), 3 Service Orientation (concentric-circles icon), 5 Configurable Enablement (sliders icon, on the right), 7 Quality & Governance (shield-with-check icon, lower-right), 6 Unified Info Exchange (left-right arrow icon, lower-left), and 4 Provisioning & Subscription (toggle-switch icon, on the left), with each principle name in bold beneath its glyph. The honeycomb arrangement and identical hex shapes deliberately avoid implying hierarchy — the figure presents the seven CCOA principles as co-equal pillars of an enterprise cloud strategy, with the gold spokes reminding readers that no single principle stands alone but each links back to the strategic core.

Figure 5.3.1

Title: Virtualization Layers — From Physical Hardware to Cloud Resources

Detailed Caption: Four horizontal bands stack vertically against a white background. The bottom navy band, "Physical Hardware (Servers | Storage | Network)," is bridged upward by short teal arrows into a teal Virtualization Layer that splits laterally into two halves — Hypervisor (VMs) on the left and Container Runtime (Containers) on the right. Above the virtualization layer sits a light-gray slot containing three navy-outlined VM tiles (VM 1, VM 2, VM 3) on the left and five smaller teal-outlined container tiles (C1–C5) on the right, with a thin dashed divider separating the two virtualization paradigms. Topping the stack is a gold-bordered "Applications & Workloads" band, fed by upward arrows from both VM and container columns, while a vertical "Abstraction" arrow runs up the right edge. By rendering the same physical foundation supporting two distinct virtualization paths, the figure makes vivid that VMs and containers are coexisting tools — the choice between them is about the right abstraction, not a competition.

Figure 5.4.1

Title: Horizontal vs. Vertical Cloud Services

Detailed Caption: Two columns stand side by side, separated by a thin dashed divider. The left column, headed in navy "Horizontal Services — Cross-Industry, General Purpose," lists five categories with mint icons: Email (Gmail, Outlook), Storage (Dropbox, Box), Collaboration (Slack, GitHub), Productivity (Google Workspace, Microsoft 365), and Databases (Amazon RDS, BigQuery). The right column, headed in teal "Vertical Services — Industry-Specific, Specialized," lists five parallel categories: Healthcare (Oscar Health, ClearDATA), Finance (Mint, Personal Capital), HR (Workday, Zenefits), Payroll (ADP, Gusto), and Pharma CRM (Veeva). A wide warm-gold band beneath both columns reads "Enterprise Cloud Strategy: Leverage Both," signaling that the comparison is not an either/or. The figure dispels the false binary the prose sometimes implies: enterprises typically run a foundation of broad horizontal utilities and layer industry-specific verticals on top, and a sound strategy budgets for both.

Figure 5.5.1

Title: Cloud Service Delivery Models — IaaS, PaaS, SaaS, and BPaaS

Detailed Caption: Four pyramidally stacked blocks rise from a wide navy base to a narrower gold cap. The bottom navy "IaaS — Infrastructure as a Service" block lists "Configure: VM sizes, storage, networking, regions"; above it, a slightly lighter navy "PaaS — Platform as a Service" block lists "Configure: runtimes, scaling rules, add-on services"; next, a teal "SaaS — Software as a Service" block lists "Configure: roles, permissions, workflows, UI, integrations"; and the warm-gold capstone, "BPaaS — Business Process as a Service," lists "Configure: pay periods, approval hierarchies, compliance rules." Two long vertical arrows flank the pyramid — the left arrow labeled "Increasing Abstraction" and the right arrow "Increasing Business Specificity," both pointing upward. The stepped narrowing makes the lesson visual: each level abstracts away more of the layer below it, so the configuration knobs progress from raw infrastructure dimensions at IaaS to business-domain decisions like pay periods at BPaaS — and choosing the right tier is choosing the right scope of decision a team wants to own.

Figure 5.6.1

Title: Unified Information Exchange Across Cloud Services

Detailed Caption: A wide teal "Integration Layer" bar — subtitled "API Gateway | Event Bus | iPaaS" — runs horizontally across the middle of the figure. Above it, four navy systems with iconified headers (CRM System, HR Platform, Analytics Engine, ERP System) drop teal connectors into the integration layer, each labeled with the protocol it speaks: REST/JSON, OAuth 2.0, Webhooks, and XML/SOAP. Below the integration layer, three light-gray downstream tiles — On-Premise Systems (Legacy, Data Warehouse), Partner APIs (Third-Party Integrations), and Mobile/Web Clients (End-User Applications) — receive arrows tagged again as REST/JSON, Webhooks, and OAuth 2.0. A gold-bordered callout pinned to the right margin lists Standards: JSON, XML, HL7 / FHIR, OCCI. The visual makes the chapter's blood-circulation metaphor concrete: by funneling diverse upstream sources and downstream consumers through one mediating layer that speaks shared standards, an enterprise can swap any single component without rewiring the others — the integration layer is what turns isolated services into a living ecosystem.

Figure 5.7.1

Title: Cloud Governance Framework — Pillars and Controls

Detailed Caption: A navy "Cloud Quality & Governance" banner across the top headers five evenly spaced teal-headed pillars beneath it. Each pillar carries a small mint icon and a four-item bullet list: Security & Compliance (Encryption, IAM, GDPR / HIPAA, Audit Logs); Cost Management (Budgets, Tagging, Right-sizing, Alerts); Quality of Service (SLAs, Uptime Targets, Latency Monitoring, Throughput); Reliability & Resilience (Multi-AZ, DR Drills, Chaos Engineering, Failover); and Operational Governance (CCoE, Policy-as-Code, Change Mgmt, Runbooks). Spanning the entire width below the pillars, a warm-gold band reads "Continuous Monitoring, Reporting & Improvement." The figure transforms governance from an abstract checklist into a structured framework — each pillar names a discipline and concrete tools, and the gold base bar makes explicit that without ongoing measurement and review the five pillars are static decoration rather than a working control system.

Figure 5.8.1

Title: Cloud Architecture Layers — From Physical Infrastructure to User Interface

Detailed Caption: Six horizontal bands stack vertically, color-graded from dark navy at the bottom to warm gold at the top. From the foundation upward: Physical Layer (dark navy, "Data Centers, Hardware, Facilities"), Virtual / Resource Layer (navy, "VMs, Virtual Networks, Storage Volumes"), Control Layer (steel-blue, "Orchestration, Auto-scaling, Kubernetes"), Service Layer (teal, "Managed Databases, AI Services, Messaging"), Application Layer (light teal, "Business Logic, Microservices, APIs"), and Presentation Layer (warm gold, "Web UI, Mobile App, API Endpoints"). Two left-side brackets divide the stack by ownership — a thin "Cloud Provider Managed" bracket spans the Physical and Virtual / Resource layers, while a taller "Enterprise Responsibility (shared)" bracket embraces Control through Presentation. The graded color and split brackets deliver the chapter's argument at a glance: the abstraction stack is also a responsibility split, with cloud-native architecture work concentrating on the upper four layers where the enterprise actually exercises judgment.