Chapter 1.3 Data Models and DBMS Architecture.ppt

Chapter 1.3: Data Models and DBMS Architecture Title: Anatomy of a Database System Authors: J. Hellerstein, M. Stonebraker Pages: 43-95 Anatomy of a Database System Problem Problem Statement Why is this problem important? Why is this problem hard? Approaches Approach description, key concepts Contributions (novelty, improved) Assumptions Problem Statement – DBMS Architecture Given A data model Platform, i.e. operating system, computer hardware architecture Find - An DBMS architecture A set of building-block components Interactions among building blocks Objectives Efficiency, Scalability Extensibility Constraints Relational Data Model Why is this problem important? Why review Relational DBMS architectural innovations? Backbone of infrastructure applications Banking, airline reservation, medical records, CRM, SCM, … Well-understood point of reference for New extensions and future revolution Architecture allows Analysis of properties Availability, fault-tolerance, reliability Mapping of multiple views User requirements to components - validation and acceptance tests Software developers, maintainer, … Software operational support group Why is this problem Hard? Complexity Mid-1970s – Efficient implementation of a Relational DBMS Declarative Query Language Logical and physical independence Changes Platforms evolve Computer Hardware, Languages, Operating Systems Storage: Tapes ? Disks (1960s) ? RAID (1990s) ? SAN … CPUs: Mainframe ? Mini ? Desktops ? Multi-core CPUs (2000s) … Integrate many views Enterprise – performance level, transaction reliability, … Data Processing Needs – data warehouses, reports, OLTP, Web,… … Contributions, Validation Methodology Contributions A simple yet relatively comprehensive RDBMS architecture Decomposition into 4 components Identification of depedencies Validation Ability to explain academic and commercial RDBMSs Expert opinion, authors have architected multiple DBMSs Proposed Approach Four Components (Figure 1, pp. 44) A Proc