IBM Software Group

1 http://tuscany.apache.org

Tuscany/SCA Value

IBM Software Group

2 http://tuscany.apache.org

Why SOA?

• Increase flexibility•The business builds services

•Coarse grained•Loosely coupled

•Business process = composed services•Services are easily replaced and recomposed to suite business changes

• Improve agility•Incorporate new requirements easily and quickly

•Reduce development time•Reduce redevelopment time•Simplify testing

• Improve ROI•Reduce function replication•Improve application consistency•Reduce cost•Reduce time

IBM Software Group

3 http://tuscany.apache.org

SOA Use Case

What I want is a standard way for describing, building, re-building, extending, deploying and managing such enterprise applications.

Intranet/Internet

POJO

EJB

BPELServlet

POJO

JSP

Javascript

Ruby

C++

Spring

XQuery

Groovy

JSONRPC

ATOM

RSS

HTTP

JMS

Web Services

Web Services

Web Services

RMI

Typical Enterprise environment

IBM Software Group

4 http://tuscany.apache.org

SOA Evolution

Less flexibleLess Agile Lower ROI

FlexibleAgile Higher ROI

Home Grown, Proprietary point to point Service-Based Technology, Standard based, example WS

Service Component Architecture (SCA), Standard based

Business logic mixed with Service call API Business logic mixed with protocol handling Single protocol enforced Typically a single technology stack enforced Cannot manage as part of the enterprise solution

Business logic separate from Service call API, handled by infrastructure Business logic mixed with protocol handling Single protocol enforced, for example HTTP Single technology stack enforced for a solution Cannot manage as part of the enterprise solution

Business logic separate from Service call API, handled by infrastructureBusiness logic separate from protocol handling, handled by infrastructure Multiple protocols supported. Protocol is a choiceMultiple technologies can be used in one solution Manage as part of the enterprise solution

Time

Brittle applications Brittle applications,

standards based Not Brittle,Standards based

IBM Software Group

5 http://tuscany.apache.org

Introducing SCA

Composite A

ComponentAService

Service BindingWeb ServiceJMSSLSBRestJSONRPCJCA…

Reference BindingWeb ServiceJMSSLSBRestJSONRPCJCA…

ComponentB

Service Interface- Java- WSDL

Reference Interface

Reference

property setting

Property

promotepromote wire

ImplementationJavaBPELPHPSCA compositespringEJB module…

- Java- WSDL

IBM Software Group

6 http://tuscany.apache.org

Why SCA makes life simpler

One way to look at SCA is that it takes all of the details of access methods, implementations, encryption, authentication, etc. and moves them into the middleware layer

Application developers write business logic, code that actually

builds value for your organization.

The details of using services are handled by SCA.

As the details change, your applications (and the developers who wrote them) aren’t affected.

IBM Software Group

7 http://tuscany.apache.org

SCA is not…

…tied to a specific programming language, protocol, technology, runtime, etc.

…a workflow model Use BPEL for that

…Web services SCA is not just web services but can happily use web services

…an ESB