Datenverwaltung mit Unity Catalog auf Databricks (Kiran Sreekumar, Karthik Subbarao)（Z-Library）

【One-Line Pitch】 A practical, hands-on guide for data architects, platform engineers, and ML/AI teams to master Databricks Unity Catalog—the industry's first unified governance system for data and AI—covering everything from identity management and access controls to regulatory compliance and open-source adoption. 【Book Arc】 - **Opening (~0%–9%)**: Introduces the strategic imperative of data and AI governance, explains why Databricks built Unity Catalog as a unified governance system (vs. piecemeal features), and sets up the book's practical approach with the fictional Nexa Boutique case study. - **Early (~16%–28%)**: Maps the full chapter structure—from architecture and identity management to compute access modes, permission modeling, AI governance, observability, data sharing, open access, compliance, and adoption acceleration—giving readers a clear roadmap of what each section covers. - **Early (~25%–34%)**: Details the target audience (data architects, application teams, cloud platform engineers, consultants, ML/AI engineers) and explains the book's typographic conventions, setting expectations for how to use the material. - **Middle (~38%–47%)**: Launches the Nexa Boutique case study—a fictional sustainable fashion e-commerce startup—showing how it invested in data lake architecture, faced regulatory pressures (GDPR, CCPA, PCI DSS), and struggled with siloed data platforms across multiple clouds. - **Middle (~47%–53%)**: Follows Nexa's journey from on-premises Apache Spark clusters to a multicloud data platform, highlighting the pain points of data silos, duplicated data in warehouses, and fragmented governance—culminating in the adoption of a lakehouse architecture with Databricks. 【Key Takeaways】 - **Unified governance is the core value proposition** (Early): Unity Catalog was built as a single governance system for the entire data and AI lifecycle—from unstructured files to ML models—rather than adding piecemeal features. This simplifies compliance and security across the board. - **Openness and interoperability are strategic pillars** (Early): Unity Catalog's open API, native support for Delta and Iceberg REST catalogs, and integration with leading formats make it a true multimodal catalog. This matters for avoiding vendor lock-in and enabling flexible data strategies. - **Identity management is foundational** (Early): The book dedicates significant attention to cloud-specific identity considerations, provisioning, single sign-on, and best practices—because getting identity right is prerequisite to effective governance. - **Compute access modes have trade-offs** (Early): Standard, dedicated, and serverless access modes each come with distinct features and limitations. Platform teams need to understand these differences to design the right infrastructure. - **AI governance is a new paradigm** (Middle): Unity Catalog extends governance to AI models and functions, covering the full lifecycle of AI systems. This is increasingly critical as generative AI adoption accelerates across enterprises. - **Regulatory compliance drives architecture decisions** (Middle): The Nexa case study illustrates how GDPR, CCPA, and PCI DSS requirements force organizations to implement region-specific governance policies—and how a unified catalog simplifies this complexity. - **Lakehouse architecture resolves data silos** (Middle): By combining data warehouse and data lake capabilities in open formats, the lakehouse model enables advanced analytics, BI, and ML from a single source of truth—eliminating the need for data duplication. 【Reading Tips】 - **Skim the foreword and preface** (~0%–9%) if you're already familiar with Databricks; the key insight is the strategic rationale for unified governance, which you can absorb quickly. - **Deep-read Chapters 3–5** (identity, compute, access controls) if you're a platform engineer or architect—these are the technical foundations that everything else builds on. - **Use the Nexa Boutique case study** (Middle, ~38%–53%) as a running example to ground abstract concepts in a concrete business scenario; it helps clarify why governance decisions matter in practice. - **Pay special attention to Chapter 10 on regulatory compliance** if you operate in regulated industries—the GDPR, CCPA, and PCI DSS discussion is directly actionable. - **Skip the acknowledgments and dedication** (~34%–38%) unless you're curious about the authors' backgrounds; they contain no technical content. 【Coverage Limits】 This guide is based on a sample of 22 of 33 indexed chunks, covering roughly the first half of the book (through ~53%). The excerpts do not cover the detailed technical implementations of later chapters (e.g., specific access control syntax, data sharing patterns, open access integrations, or migration procedures), which are only summarized in the chapter overview.