What Does Service Data Objects (SDO) Mean?
Service Data Objects (SDO) is a framework providing convenient and uniform layer to access data from a wide range of data sources.
Data sources include relational databases, XML, Web services and enterprise information systems. It allows programmers to access and manipulate data from these data sources in a unified manner.
SDO has many important and useful features, including:
1. Reducing the number of data APIs, thereby simplifies the J2EE data programming model
2. Streamlining the processing of Service-Oriented Architecture (SOA)
ecoupling of application code from data access code
4. Providing support for XML and also integrating XML.
5. Providing metadata API
Techopedia Explains Service Data Objects (SDO)
SDO was originally developed by IBM and BEA as a joint collaboration in 2004, with the approval by Java community process. It was officially released as a specification in November 2004, which later became a part of Service Component Architecture (SCA). SDO technology was earlier known as Web data objects (WDO). The idea behind SDO design is based on the concept of disconnected data graphs. A data graph consists of tree and graph structured data objects. In disconnected data graphs architecture, data is organized as graphs, which are retrieved from data source by clients. Changes are incorporated in data graphs. These changes are updated back in data source. The applications are connected to data sources by data mediator services.
SDO was designed to be language-neutral and to be available in different languages. It has the ability to support a disconnected programming model. It facilitates both static and dynamic types of programming models. SDO is available in a wide range of programming languages such as C, C++, COBOL and JAVA.
Some of the major benefits of SDO are:
1. Simplified and unified programming across different data sources
2. Providing robust support for applications having common patterns
3. Facilitating applications to handle and query data easily
4. Being XML friendly
5. Capable of metadata introspection