 - 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.
 |
Learn more about Service Data Objects (SDO) |
| SCA and SDO standards: I've seen offerings from both IBM (fabric) and Tibco (Matrix) over the last few months that are leveraging this "managed container" approach for service abstraction. What are your thoughts on the SCA ... |
| 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 services mashups. |
| SOA standards WS-Policy, SCA and SDO advancing rapidly: Emerging SOA standard WS-Policy 1.5 is a proposed recommendation at W3C, while technical committees form to standardize SCA and SDO at OASIS. |
| SCA and SDO become SOA essentials for banking system: SCA and SDO, which last month began moving through the standards process at OASIS and JCP, are already being implemented in a bank processing system. |
| SOA specs SCA and SDO headed for OASIS and the JCP: The Open SOA group has finally found a standards body homes for its two key specifications, Service Component Architecture (SCA) and Service Data Objects (SDO) at OASIS and JCP. |
| The top SOA/Web services stories of 2006: This two part year-in-review articles includes WS-Policy, agile development, the changing ESB and Eclipse getting more involved with SOA and Web services |
| 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 services mashups. |
| SCA and SDO for PHP: Daniel Rubio takes a look at what Service Component Architecture and Service Data Objects can offer PHP applications. |
| Technological independence with SCA and SDO: This article discusses the introduction of Service Component Architecture (SCA) and Service Data Objects (SDO). |
| SDO - Service Data Objects: In this tip, Daniel Rubio discusses the reasons why Search Data Objects was created. |
| LAST UPDATED: |
31 Aug 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
 |
 |
| |
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...
|
|
|
Show me everything on 