GridEnabled Sedna XML DBMS

1
Grid-Enabled Sedna XML DBMS

• Pervin Artem

GeonGRID Workshop, June 25-26 2007, Moscow
2
Sedna DBMS

• Why Sedna?
• Open Source, ISP RAS
• Native XML Database (NXD)
• High performance
• Good user support

3
OGSA-DAI

• Open Grid Services Architecture Database Access
  and Integration ? an open and widely used tool
  for data sources integration using web-services
• OGSA-DAI a set of service-oriented interfaces
  for accessing relational and semistructured (XML)
  data

4
3 ways to integrate a custom DBMS into OGSA-DAI

• Based on XMLDB API standard
• Based on specialized service (Grid Data Service,
  GDS)
• Based on standard OGSA-DAIs Activities

5
XMLDB API

• Implementation of XMLDB API
• OGSA-DAI uses XMLDB API to access XML DBMS
  (eXist, Xindice)
• However XMLDB API is outdated (last update 2003)
• Too complex

6
Specialized service overview

• Pros
• Less levels of abstractions more performance
• Cons
• Sedna have nothing in common with other XML
  DBMSes
• Hard to federate

7
Standard OGSA-DAI Activities

• Single point of entry for various data sources
• Equivalence of response-documents for equivalent
  queries to different DMBSes
• Extendable list of supported DBMSes
• Ability to federate data-sources

xPathActivity
XMLDB API
Sedna API

Xindice
eXist
Sedna
8
Supported Activities

• xPathActivity
• Query data sources using xpath
• SednaBulkLoadActivity
• Load new documents into data source

9
Open Issues

• Limitations of xPath lack of grouping, sorting,
  joins, etc
• Mapping the base collection to document
• XUpdate not supported in Sedna
• Collection management

10
Proof of concept

• Experiments with heterogeneous data sources
• DBMSes eXist ? Sedna.
• Same test document.
• Same perform-document.
• ? Equivalence of response-document.

11
Thank you for your time!