 - Service Data Objects (SDO) is the name of a specification designed to streamline the processing of SOA (service-oriented architecture) data from diverse sources such as XML documents, relational databases and Web services. SDO can be used with static or dynamic interfaces, making it convenient for application programmers.
Key features of SDO include separation of data access code from application code, implementation of customized data access layers and support for disconnected programming models. SDO organizes data as graphs containing units called objects that can be easily updated, allowing constant and reliable access to data from all sources.
SDO began as a joint collaboration between IBM (International Business Machines) and BEA Systems, Inc. and was published officially as a specification in November 2004. Later, SDO was included as part of the SCA (service-component architecture). SDO is evolving as an increasing number of key industry players contribute to the development of new versions.
| LAST UPDATED: |
31 Aug 2007
|
 |
Read more about Service Data Objects:
|
|
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
 |
 |
| |
RELATED CONTENT
 |
SCA and SDO standards
David Linthicum defines Service Component Architecture (SCA) and Service Data Objects (SDO) and explains how to best build these components to enable...
|
|
Apache releases Java SCA
The Apache Tuscany team announced the 0.99-incubating release of the Java SCA project, a runtime based on the Service Component Architecture...
|
|
Using ADO.NET and SDO for SOA data continuity
Both ADO.NET and SDO use XML to enable data transfer between disjointed components inside an SOA, enabling developers to create all kinds of new Web...
|
|
|
