Enterprise Architecture for Digital BusinessTransforming IT (Lin, GengMacVittie, Lori A.) (Z-Library)

# Enterprise Architecture for Digital Business: Transforming IT ## 【One-Line Pitch】 A practical framework for CIOs, IT directors, and architects who need to evolve their enterprise architecture to support a fully digital, data-driven business—balancing stable core operations with rapid innovation at the edge. ## 【Book Arc】 - **Opening (~0%–10%)**: Establishes the "Innovation Equation"—the tension between keeping core business stable while innovating at the edge—and outlines why traditional enterprise architecture frameworks (like TOGAF) are no longer sufficient for the accelerated pace of digital transformation. - **Early (~10%–32%)**: Introduces the digital enterprise architecture framework with six domains—Business, Application Delivery, Data, Technical, Operations, and Security—and explains how these replace or extend the traditional four-domain model (Business, Application, Data, Technology). - **Middle (~32%–48%)**: Explores the infrastructure renaissance driven by cloud, edge computing, and microservices, showing how the traditional assumption of centralized users and fixed locations has collapsed in favor of distributed, mobile, and highly connected environments. - **Middle (~48%–65%)**: Examines application delivery as a core IT discipline, the expansion of data to include operational telemetry, and the rapid evolution of security practices to address modern attack surfaces and supply chain risks. - **Late (~65%–90%)**: Covers observability, automation, and SRE operations as essential capabilities for operating at scale, with a focus on meeting business service-level objectives (SLOs) through telemetry-driven, automated operations. - **Ending (~90%–100%)**: Synthesizes the argument that digital transformation changes everything about how IT must be architected, operated, and governed—requiring a holistic, domain-based approach rather than piecemeal technology adoption. ## 【Key Takeaways】 - **Digital transformation accelerated nearly tenfold between 2019 and 2020** (Early): The pace of change is driven by wireless access, smartphone platforms, cloud-based applications, constrained engineering talent, and customer demand for better experiences—all pointing to an increased need for innovation. - **Traditional enterprise architecture frameworks are insufficient** (Early): The classic four-domain model (Business, Application, Data, Technology) served organizations well into the internet age but must evolve to include new domains like Application Delivery, Operations, and Security to support digital business. - **The digital enterprise architecture framework has six domains** (Early): Business, Application Delivery, Data, Technical, Operations, and Security—each with specific responsibilities, from defining SLOs for digital experiences to governing privacy and compliance across every architectural domain. - **Infrastructure is undergoing a renaissance** (Middle): The shift from centralized data centers to distributed cloud, edge, and endpoint locations means infrastructure must be treated as a programmable, software-defined resource rather than fixed hardware. - **Microservices adoption delivers measurable benefits** (Middle): Organizations report faster deployment (69%), greater flexibility (61%), and rapid scaling of new features (56%)—but these benefits require merging infrastructure and application constructs to eliminate traditional provisioning barriers. - **Operational data is the new oil** (Middle): Moving from agent-based, siloed monitoring to open, standards-based approaches enables centralized data lakes for operational telemetry, which supports better forecasting, capacity planning, and insight generation. - **Security must be embedded across the entire architecture** (Middle): With the average modern application containing 128 open source dependencies, security can no longer be a single-function team's responsibility—it must be woven into every domain and team. - **SRE operations is a domain, not just a role** (Late): Site reliability engineering applies software engineering principles to infrastructure and operations problems, fulfilling the need identified by 65% of technology leaders for real-time digital operations to accelerate innovation. ## 【Reading Tips】 - **Skim the introduction and Chapter 1** for the core argument and framework overview; this is where the authors define the problem and introduce the six-domain model that structures the rest of the book. - **Deep-read Chapters 2–4** if you're focused on infrastructure, application delivery, and data—these chapters contain the most concrete technology trends and practical implications for architecture decisions. - **Pay attention to the "Form Follows Function" principle** in Chapter 1; it's the conceptual anchor for why enterprise architecture must change in response to technological shifts, not the other way around. - **Treat the book as a framework, not a prescriptive guide**—the authors explicitly state they don't offer implementation details, so use it to align your architectural thinking and identify gaps in your current approach. - **Read the Afterword last** to reinforce the overall thesis; it ties together the argument that digital transformation is not a one-time project but an ongoing evolution of how IT operates. ## 【Coverage Limits】 This guide covers the book's core framework and domain-level discussions based on available excerpts. Specific implementation details, case studies, and the full depth of Chapters 5–7 (security, observability/automation, and SRE operations) are only partially represented in the source material. ##