SOA6: Standards for ServiceOriented Architecture

1
SOA-6 Standards for Service-Oriented Architecture
Glen Daniels
Standards Strategist, Sonic
2
Agenda

• SOA in a Nutshell
• The Need for Standards
• The Standards Landscape
• Key Standards for SOA Today
• Mediation A Brief Interlude
• Key Standards for SOA Tomorrow
• Summary

3
SOA in a Nutshell (ities)

• SOA Modularity
• SOA Composability
• SOA Interoperability
• Same Old Architecture?
• Coarse-grained businesscomponents

4
Shared Models Interoperability

• Physical communication channels
• Data formats
• Protocol framing / MEPs
• QoS (security, reliability, etc)
• Component interfaces
• Policies
• Semantics
• ALL of this needs to be agreed upon!

5
The Need for Standards

• Standards provide the common structure components
  require in order to work together
• Standards are the fuel which makes SOA go

6
Landscape Types of Standards

• Wire-level standards (WS-)
• Data standards (XML, SQL, ProDataSet)
• API standards (DOM, JAX-RPC, Apache)
• Behavioral standards (WS-Notification, etc.)
• Metadata standards (WSDL, Policy)
• Design standards (UML)
• Also De Facto / De Jure

7
Landscape Whos Working on What?

• World Wide Web Consortium (W3C)
• XML, Web Services core, Semantic Web
• OASIS
• WS-
• WS-I
• Interoperability profiles
• JCP
• Java APIs
• Open Source Communities
• De facto standards (Apache, Eclipse, etc)

8
Specifications ! Standards

• Open Standards consortia are the best places to
  get tech
• IPR policy is clear
• Community has had a chance to vet specs
• but innovation requires that consortia arent
  the only place to get tech
• Individual companies, or small groups publish
  specs before standardization
• Distributed evolution is great, just be careful

9
Key Standards For SOA Today WSDL

• Web Service Description Language

• Machine readable contract
• Metadata about services

• Address of endpoints
• Interface
• Message structure
• Data types

10
Key Standards For SOA Today SOAP
ltHeadersgt

• XML Envelope with Headers and Body
• Headers contain extensions security,
  transactions, etc

• Processing Model with mandatory or optional
  extensions
• Bindings to protocols like HTTP, Email, JMS, etc

ltBodygt
11
Key Standards For SOA Today WS-Addressing

• SOAP version of familiar concepts TO, FROM,
  REPLY-TO, etc
• Endpoint References can contain policies,
  metadata, cookies (Reference Parameters)

• Allows responses to be delivered along separate
  connections (asynchronously)
• Allows composition of multiple interactions
  (process)

12
Key Standards For SOA Today WS-Policy

• Capabilities and Requirements metdata
• I support reliability
• I require authentication

• Group sets of assertions into policies
• Refer to policies from WSDL, in EPRs, etc.

ltwspPolicygt lt/wspPolicygt
13
Key Standards For SOA Today WS-Security

• Message-level security
• Encryption
• Authentication (XML Digital Signature)
• End-to-end, not point-to-point

• Profiles for simple uname/password, SAML,
  Kerberos, etc

14
Key Standards For SOA Today WS-RM
A
B

• Builds reliable sequences of messages over
  unreliable transports

• Needed to ensure duplicate detection, ordering,
  etc

15
Web Service Patterns Bindings

• Web services can be bound to different
  underlying protocols
• Bindings also provide the ability to control
  policy/metadata
• Separation of concerns
• This provides a lot of flexibility the same
  abstract model can be used while the underlying
  implementation is switched/updated over time

16
Web Service Patterns MustUnderstand

• Extensions can be optional (this is available) or
  mandatory (you must do this).
• Allows extensions to CHANGE critical behaviors in
  a safe way
• Must understand allows distributed extensibility
• Different extensions at different times, from
  different sources
• This model allows fast fail, which really helps
  us humans do debugging

17
Wheres My Flying Car?

• How far along is all this anyway?
• Basic WS mostly works today
• Advanced WS almost there
• Policy-driven process-oriented integration will
  take a little longer
• Even when a stack has stabilized, change will
  be a factor (thank goodness!)

18
Mediation A Brief Interlude
Service
Consumer
Intermediary
19
Mediation Benefits

• Limits unnecessary tight coupling
• Separates concerns
• Manages evolution
• Insulates you from external changes
• Allows you to make internal changes
• Leverage existing assets in new ways
• Adapts message patterns, protocols, data formats,
  etc.

20
Mediation The Enterprise Service Bus
21
Key Standards for SOA Tomorrow

• Eventing / Notification
• Asynchronous event processing
• Management (WSDM/WS-Management)
• Interoperable control and monitoring
• Business Process Execution Language (BPEL)
• Process sharing
• SCA
• Language-neutral application assembly model
• XQuery
• Rich language for manipulating XML data

22
In Summary

• SOA is an architectural pattern that needs
  standards to make it real and interoperable
• Web Services are the way that happens (for today)
• Architecture lasts, though individual standards
  will evolve
• Use OpenEdge Reference Architecture
• Mediate and insulate!

23
Relevant Exchange Sessions

• SOA-12 OpenEdge Web Services
• David Lund
• INNOV-5 Web Services Management Monitoring
• Dan Foody
• INNOV-10 Introduction to XQuery
• Gus Bjorklund

24
Questions?
25
Thank you foryour time
26
(No Transcript)