Building next-generation SOAs with SCA and SDO

	Select location and register

	Get the agenda and presentations

As Service-Oriented Architectures continue to grow and mature, developers and architects are faced with an ever-growing number of programming interfaces, transports, data sources and other details. Service Component Architecture (SCA) and Service Data Objects (SDO) provide a single programming interface for a wide variety of services and data sources. In this briefing, you'll see how the simplicity of SCA and SDO lets you focus on things that matter to your organization, not on the details of particular APIs.

Audience

Architects and developers who want to understand the technologies that will drive the next generation of SOA.

Objectives

• Discuss the current state of Service-Oriented Architectures and its growing pains.
  
  
• Explain the rationale behind Service Component Architecture and Service Data Objects and how these technologies simplify the development, testing and deployment of SOA applications.
  
  
• Demonstrate the technology in action with examples running on the Apache Tuscany project, an open-source implementation of SCA and SDO.
  
  
• Illustrate how SCA and SDO work with BPEL, the Business Process Execution Language. The combination of SCA, SDO and BPEL enable the greatest flexibility in Service-Oriented Architectures.
  

Duration

Half day

Details

Service Component Architecture provides a single interface to many different kinds of services and access methods. If a service is (for example) a Web service, a BPEL process, a C++ class or a POJO, you write the same code to access all of them. If that service is accessed via SOAP, a messaging system such as JMS, or as a local object, you write the same code to access all of them. If that service requires authentication, encryption or some other policy, your code doesn't change. SCA gives your applications more flexibility than you've ever had before.

Service Data Objects provides a similarly elegant solution to data access. With SDO, you have a single interface to your data source, whether it's a relational database, an XML file, a Web service or something else (an LDAP directory, for example). SDO lets you use a single API, regardless of the underlying technology.

In this briefing, we'll look at the theory behind the technology, and we'll also use a sample application to illustrate the concepts behind SCA and SDO. The running code is based on the Apache Tuscany project, an open-source implementation of SCA and SDO. The underlying middleware is also open-source.

You'll leave with an understanding of what these new technologies are, how they work and how they can make your organization more nimble and responsive than ever.

Downloads

	Information about download methods			Get Adobe® Reader®

Resources

• Specifications: SCA and SDO.
  
  
• The whitepaper "The Business Value Proposition of SCA", along with many other papers and articles.
  
  
• The Apache Tuscany project, an open-source implementation of SCA and SDO.
  
  
• SOA and Web services on developerWorks.

Back to top