ieee icde 2003 panel organic databases to support an ambient world (mk/icdepanel.pdf) organic...

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Disappearing DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

The database system is gone?

• Data management can be left to the individual applications

• There is no need for a down-scaled SQL DBMS

• Data management does not require a DBMS

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Reappearing DBMS• Phase I: The DBMS is hidden in the wall?

– SQL/XML the language inter-galactica?– Local communication/functionality bottlenecks?– Single point of failure ?– Dinosaurs of software systems ?– Limited market ? Locking to a single manufacturer?

• Phase II: Every product his own DBMS ?– What sensors should a DBMS have ?– How to communicate amongst peers ?– What happens if the DBMS is crushed ?– How to ensure a multi-year backward compatibility ?

• What are the ingredients of the next generation DBMSs?

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Organic Database System characteristics

• Self-descriptiveness• An outsider (software package) can easily access, interpret,

and re-use the database schema governing its content

• The resource requirements/limitations in terms of hw/sw/cw footprint, processing speed, energy, etc.. are explicitly stated and part of the database schema.

• The software version trail of the data manager is available in a form which permits traveling back in time, both wrt the governing schema and the database content.

• The code-base of the database manager is part of the database store itself

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Organic Database System characteristics

• Self-organizing, – the system is able to split its activities into disjoint, yet coherent

subsystems with minimal synchronization requirements

– Systems can easily fuse, reconciling the differences where evident, with user interaction to resolve conflicts.

– roll-forward over schema updates; automatic storage optimization (indices)

– the database can easily migrate, be replicated or moved to another location without loosing control over the trail of instances left behind

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Organic Database System characteristics

• Self-repair,• A runable DBMS version can be obtained on any new

platform with a minimal bootstrap procedure, e.g. building a VM or producing code for the target

• The software is set-up in such a way that a bug can be resolved by locking out part of the code base without sacrificing the functionality

• The system uses a replicated storage/indexing scheme with different point-of-failure techniques to recover from hw/sw/cw failures

• The system manages a trail of database versions and is able to synchronize different trails (controlled fusion of data stores)

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

Organic Database System characteristics

• Self-awareness• Security aware. It should be able to authenticate the direct

environment only. This does not exclude schemes based on encryption to exchange information or to limit access.

• Location aware. It knows its position in a group of peers, possibly it has access to the GPS coordinates.

• Time-aware, in the sense that it organizes both past and possible futures; e.g, conflicts are essential previews of a possible consistent alternative futures. Likewise, history can lead to multiple views and interpretations. It should be possible to manually go back in time.

IEEE ICDE 2003 Panel Organic Databases to support an Ambient world (www.cwi.nl/~mk/icdepanel.pdf)

A grand challenge for the 21st centrury !!!

Develop an organic database management system which can be embedded in a wide collection of hardware appliances and provides an autonomous self-descriptive, self-organizing, self-repairable, self-aware and stable data store-recall functionality to its environment