Transcript Tuscany SCA Value - Apache Software Foundation

IBM Software Group
Tuscany/SCA Value
1
http://tuscany.apache.org
IBM Software Group
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
2
http://tuscany.apache.org
IBM Software Group
SOA Use Case
Typical Enterprise environment
Groovy
HTTP
JSP
Web
Services
JSONRPC
POJO
Servlet
RMI
ATOM
Javascript
RSS
Spring
POJO
JMS
BPEL
EJB
Web
Services
Ruby
Web
Services
Intranet/
Internet
C++
XQuery
What I want is a standard way for describing, building, re-building,
extending, deploying and managing such enterprise applications.
3
http://tuscany.apache.org
IBM Software Group
SOA Evolution
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 infrastructure
Business logic separate from protocol
handling, handled by infrastructure
Multiple protocols supported. Protocol
is a choice
Multiple technologies can be used in
one solution
 Manage as part of the enterprise
solution
Brittle applications
Brittle applications,
standards based
Not Brittle,
Standards based
Time
Flexible
Agile
Higher ROI
Less flexible
Less Agile
Lower ROI
4
http://tuscany.apache.org
IBM Software Group
Introducing SCA
Service Interface
- Java
- WSDL
Reference Interface
- Java
- WSDL
Property
Composite A
property setting
Component
A
Service
promote
Component
B
wire
Service Binding
Web Service
JMS
SLSB
Rest
JSONRPC
JCA
…
Implementation
Java
BPEL
PHP
SCA composite
spring
EJB module
…
5
http://tuscany.apache.org
Reference
promote
Reference Binding
Web Service
JMS
SLSB
Rest
JSONRPC
JCA
…
IBM Software Group
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.
6
http://tuscany.apache.org
IBM Software Group
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
7
http://tuscany.apache.org