1 / 27

Chapter 9. Systems

Chapter 9. Systems. Seoul National University Department of Computer Engineering OOPSLA Lab. Table of Contents. GemStone Iris ObjectStore O 2 ORION Vbase. GemStone. Servio Logic Development Corporation Aim provide DBMS with a very powerful data model

emma
Download Presentation

Chapter 9. Systems

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. Chapter 9. Systems Seoul National University Department of Computer Engineering OOPSLA Lab.

  2. Table of Contents • GemStone • Iris • ObjectStore • O2 • ORION • Vbase

  3. GemStone • Servio Logic Development Corporation • Aim • provide DBMS with a very powerful data model • reduce the time for developing complex applications • Smalltalk-80 + functions of DB

  4. GemStone Model • Almost completely identical to the Smalltalk-80 model • Key concepts • object, class, and message • Languages • OPAL • extension of Smalltalk-80 • DML/DDL • C, C++ and PASCAL

  5. GemStone System Architecture

  6. GemStone Client • OPE(OPAL Programming Environment) • Class Browser • Bulk Loader/Dumper • Workspace Editor • PIM(Procedural Interface Modules) • object modules which can be called from application programming languages • implementation of remote procedure calls to the functions provided by server

  7. GemStone Server • Gem • object memory • standard Smalltalk virtual machine • compiles and executes methods • session control and authentication • Stone • management of secondary storage and work areas • concurrency control, transactions, and recovery • authorizations • associative access

  8. Iris • HP laboratories • Implemented in C language on HP-9000/320 UNIX workstation • Office system, knowledge bases and HW/SW design

  9. Iris Model • Key concepts • Objects • Type: class, multiple inheritance • Function • No distinction between attributes and methods • both are seen as functions • Functions does not, in fact, belong to the types • functions can be specified which are defined in relation to several types

  10. Iris Interfaces • Programming interface • Interactive interface • OSQL • Object-oriented SQL extension • Iris Inspector • extension of the LISP structure browser • front-ends for C and LISP • all interfaces are based on a set of C subroutines which implement the object manager interface

  11. Iris Systems Architecture • Object manager • implements the Iris OO model • the definition and manipulation of schema and query management • Secondary storage manager • transactions with save points and rollbacks • concurrency control • file and index management

  12. ObjectStore • Object Design Inc. • Simplify conversion of existing applications and for advanced application areas such as CAD, etc • Provide high performance levels • virtual memory with page-fault • highly portable • Interface • no direct support for SQL • by programs written in C/C++ with an interface library

  13. ObjectStore System Architecture • Client/server architecture • clients are high-level PCs and workstations • Server can support different architectures on the same network • System consists of : • ObjectStore DBMS • ObjectStore run-time • Schema Designer/Browser • a DML built as a C++ preprocessor

  14. O2 • Altair consortium • O2 Model • flexible • complex value • exceptional object

  15. O2 Languages • Application Programming language • CO2 : extension of C • Basic O2 : extension of the Basic language • Persistence of objects in O2 is orthogonal to class • instances of a class are not necessarily persistent • complex values can be transformed to be persistent

  16. O2System Architecture • Schema manager level • creation, access, modification and deletion of schema • consistency of schema • Object manager level • objects and complex values • message exchange • persistence, garbage collection, access, and clustering • transaction management • WISS(Wisconsin Storage System)

  17. Alphanumeric Interface COPE Query Interface LOOKS Language Processor Schema Manager Object Manager WISS

  18. O2 Environment and Tools • Language Processor • Query Processor • Interface generation environment(LOOKS) • Programming environment(OOPE) • Alphanumeric Interface

  19. ORION • Microelectronics and Computer Corporation(MCC) • First version • single-user system • implemented in Common Lisp • Second version • multi-user system, distributed architecture • public database • private database

  20. ORION System Architecture • Message handler module • handling all messages sent to the ORION • Object subsystem module • highest level of functions such as schema modification, version control, and query optimization, etc. • Storage subsystem module • management of objects on disk • Transaction subsystem module • all functions for transaction management including concurrency control and recovery

  21. Vbase • Ontologic Inc, SunOS 3.2 UNIX • OO development system • OO procedural language + persistent object management • Model • abstract data types • multiple inheritance • Interface languages • TDL(Type Definition Language) • COP(C Object Processor)

  22. Vbase Systems Architecture • Language level • Abstraction level • Representation level • Storage level

  23. Characteristics of Vbase • Typed exceptions • Application development tools • debugger • interactive object editor • a program which checks the consistency of the physical structure of the object space • DBMS functions • clustering a set of objects • defining the inverse of a given attribute • customizing access to an attribute

More Related