1 / 12

Outline

Outline. Introduction Background Distributed DBMS Architecture Distributed Database Design Distributed Query Processing Distributed Transaction Management Building Distributed Database Systems (RAID) Mobile Database Systems Privacy, Trust, and Authentication Peer to Peer Systems.

kurt
Télécharger la présentation

Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Outline • Introduction • Background • Distributed DBMS Architecture • Distributed Database Design • Distributed Query Processing • Distributed Transaction Management • Building Distributed Database Systems (RAID) • Mobile Database Systems • Privacy, Trust, and Authentication • Peer to Peer Systems

  2. Useful References • B. Bhargava and John Riedl, The Raid Distributed Database System, IEEE Trans on Software Engineering, 15(6), June 1989. • B. Bhargava and John Riedl, A Model for Adaptable Systems for Transaction Processing, IEEE Transactions on Knowledge and Data Engineering, 1(4), Dec 1989. • B. Bhargava, Building Distributed Database Systems. • Y. Zhang and B. Bhargava, WANCE: Wide area network communication emulation systems, IEEE workshop on Parallel and Distributed Systems, 1993. • E. Mafla, and B. Bhargava, Communication Facilities for Distributed Transaction Processing Systems, IEEE Computer, 24(8), 1991. • B. Bhargava, Y. Zhang, and E. Mafla, Evolution of a communication system for distributed transaction processing in RAID, Computing Systems, 4(3), 1991.

  3. Implementations • LOCUS (UCLA) File system OS • TABS (Camelot) (CMU) Data servers OS • RAID (Purdue) Database level (server) • SDD-1 (Computer Corp. of America) Transaction manager Data manager • System – R* (IBM) Database level • ARGUS (MIT) Guardian (server)

  4. site j, k, l,… User Transaction . . . . . . . . . . Database after commit log//diff file Parser read only compiled transactions updates Action Driver (interpret transactions) Action Driver (interpret transactions) compiled transactions Action Driver (ensure transaction atomicity across sites) Atomic Controller abort or commit compiled transactions Concurrency Controler Action Driver (ensure serializability) Architecture of RAID System

  5. Query Language DBMS completed transactions Atomicity Controller Atomicity Controller Atomicity Controller Concurrency Controller RAID Transactions

  6. RAID Distributed System DBMS other applications DBOS other applications RAID OS OS • RAID supports reliability • transactions • stable storage • buffer pool management

  7. Local Database User Process (UI and AD) (2 messages) TM Process (AM, AC, CC, RC) (2 messages) Remote RAID Sites Transaction Management in one Server

  8. CPU time used by RAID servers in executing transactions

  9. RAID Elapsed Time for Transactions in seconds

  10. RAID Execution Time in seconds

  11. Performance Comparison of the Communication Libraries

  12. Experiences with RAID Distributed Database • Unix influences must be factored out. • Communications software costs dominate everything else. • Server based systems can provide modularity and efficiency. • Concurrent execution in several server types is hard to achieve. • Need very tuned system to conduct experiments. • Data is not available from others for validation. • Expensive research direction, but is respected and rewarded.

More Related