Object Oriented Databases Abhishek Khanolkar Agenda l Service

Object Oriented Databases Abhishek Khanolkar

Agenda: l Service and SOA. l Object oriented Databases. l Different Architectures MOCHA, SODA. l Compare. l Conclusion. l Questions?

Services? l In everyday life Cooking, hairdressing and cleaning. l Something that adds value to the inputs and gives an output. l A service is an encapsulated method. l Service could be used to insert and retrieve data from database.

Web Service and SOA. l Web Service enable machine to machine interaction. l Web service make use of WSDL, XML and SOAP. The protocol is HTTP, JMS. l SOA is a collection of distributed, self contained web services.

Middleware Systems. l TIBCO. l IBM MQ l Web Methods. l RPC. l JEE. l CORBA. l JMS/MOM.

SOA + database <=Service oriented Databases. l Service need data. l Data Integration Servers. l Database Gateway and Database Mediator. l Wrappers? What are they?

Service Oriented Databases & Database Middleware. l System to integrate collection of data over networks. l Current system is architected around Data Integration Servers. l Uniformity is achieved by imposing Global data View on top of local data view. l There are 2 ways to do that database gateway and database mediator.

Service Oriented Database cont… l Database Gateway accesses the remote data. l Database Mediator does distributed query processing. l Mediator make use of wrappers to access and translate the data into Global Data Model.

MOCHA. l MOCHA is a self-extensible middleware system. l The new application-specific functionality for query processing is deployed to remote sites in a automatic fashion. l Existing middleware systems will ship the data or evaluate operators already present in the environment.

MOCHA Architecture.

QPC

DAP

SODA l The SQL Server SODA has following features— l SQLCLR l Database Change Notification. l Native Web Service Access l Service Broker.

SODA – SQLCLR

SODA-- DCN

SODA – Native Web Service Support

MOCHA Vs SODA l MOCHA offers memory management and object reuse. l SODA in SQL Server offers only memory management. l MOCHA was used in university of Maryland, SODA is effectively implemented in the 2007 version of SQL Server.

MOCHA Vs SODA l MOCHA is self-extensible, SODA is NOT. l SODA uses the Database Integration Server. l MOCHA uses the java Sockets, QPC and DAP.

References. l l l [1] Gennaro (Jerry) Cuomo, IBM SOA “on the Edge” SIGMOD 2005. [2] Mira Kajko-Mattsson, Grace A. Lewis, Dennis B. Smith, A Framework for Roles for Development, Evolution and Maintenance of SOA-Based Systems, International Workshop on Systems Development in SOA Environments (SDSOA'07), 2007 [3] Dov Dori, SODA: Not Just a Drink! From an Object-Centered to a Balanced Object-Process Model-Based Enterprise Systems Development, Proceedings of the Fourth Workshop on Model-Based Development of Computer-Based Systems and Third International Workshop on Model-Based Methodologies for Pervasive and Embedded Software, 2006 [4] Web Services Architecture, http: //www. w 3. org/TR/2004/NOTE-ws-arch 20040211/ 2004 [5] Manuel Rodr´ıguez-Mart´ınez, Nick Roussopoulos, MOCHA: A Self. Extensible Database Middleware System for Distributed Data Sources_, MOD 2000, Dallas, TX USA [6] David Campbell, Service Oriented Database Architecture: App Server. Lite? , SIGMOD 2005,