SODA!
During the SQL Server 2005 Tokyo Launch, Prof. Jim Gray presented an overview of the evolution of DBMS architectures (a must read for all those interested in how much progress we have made in DBMS research and how much of these have been successfully transferred into commercial products like SQL Server 2005!)
One of the most interesting issues discussed was Service Oriented Data Architecture (SODA). SODA differents between different types of data in this new architecture, as follows:
- RESOURCE: Data that is the "master data" for the enterprise
- REFERENCE: Data that is a copy of the resource data and widely distributed in caches
- SERVICE: Data that are the messages exchanged between clients and services
- ACTIVITY: Data records of what happens in the system
SODA then uses this different types of data in its design for federated data services that are event driven, loosely-coupled and heterogeneous. All communication will be achieved via service data messages. This is probably a natural transition between the advances in web services and DBMSs. He sees SQL 2005 as a web service container which talks WS (e.g SOAP/WSDL/WS-Security) etc, as well as a service broker.
To me, one of the thots that pop into my mind was "What exactly is a DBMS?" Is it still a monolithic core? Or does it merely consists of a set of local primitive data services and query processing is achieved by through efficient composition of web services? In traditional DBMS architecture, there is a notion of Storage Management which handles the management of the data pages. In SODA, how would this Storage management layer change?
One of the most interesting issues discussed was Service Oriented Data Architecture (SODA). SODA differents between different types of data in this new architecture, as follows:
- RESOURCE: Data that is the "master data" for the enterprise
- REFERENCE: Data that is a copy of the resource data and widely distributed in caches
- SERVICE: Data that are the messages exchanged between clients and services
- ACTIVITY: Data records of what happens in the system
SODA then uses this different types of data in its design for federated data services that are event driven, loosely-coupled and heterogeneous. All communication will be achieved via service data messages. This is probably a natural transition between the advances in web services and DBMSs. He sees SQL 2005 as a web service container which talks WS (e.g SOAP/WSDL/WS-Security) etc, as well as a service broker.
To me, one of the thots that pop into my mind was "What exactly is a DBMS?" Is it still a monolithic core? Or does it merely consists of a set of local primitive data services and query processing is achieved by through efficient composition of web services? In traditional DBMS architecture, there is a notion of Storage Management which handles the management of the data pages. In SODA, how would this Storage management layer change?
posted by SQL Server Gems at
5:02 PM
0 Comments:
Post a Comment
<< Home