Current State of Affairs in SOA Along with Migration Strategies and Methodologies

1
Current State of Affairs in SOA Along with
Migration Strategies and Methodologies
www.oasis-open.org
John Harby
2
John Harby

• John Harby is currently working with MIRO
  Technologies, a global aerospace defense
  contractor headquartered in San Diego. He
  specializes in the SOA and middleware areas. He
  is a member of several OASIS Technical Committees
  and is also on several JSR expert groups.
• He was co-author of The Middleware Company SOA
  Blueprints initiative. He has previously worked
  in product development for vendors including
  Oracle, BEA Systems and was a Sr. Architect in
  the HP Web Services (e-speak) lab. His first
  experience in SOA was in the mid-90's developing
  systems for U.S. Intelligence using CORBA/C

3
PGFSOA

• Practical Guide to Federal SOA
• Are using OASIS standards such as the SOA
  Reference Model
• lthintgtStill accepting volunteerslt/hintgt

4
The Standards have Arrived

• OASIS SOA RM, SCA, SDO
• WS-Transaction
• WS-Addressing
• Etc.

5
Product Maturity

• Orchestration IBM, BEA, Oracle, et al are
  maturing
• Registries, ESBs, etc. also no longer new
• Many support tooling now exists, e.g. management
  tools

6
Open Source Contributions

• JBoss jBPM, ESB
• Mule ESB
• ServiceMix
• Synapse

7
External to Technology

• Governance
• Methodologies
• Management

8
REST Approach

• Further decoupling through abstraction of
  contract
• Lack of declarative standardization
• Can one use REST within SOA?

9
Practices, What Works?

• Choose pilots carefully
• Governance always comes first
• Vendor selection matters even more

10
Practices, What Works?

• SOA as a pattern
• Migration strategies
• Platform integration

11
Novel approach AOP/SOA

• Services can be woven rather than orchestrated.
• Especially useful for lightweight services with
  many join points.
• Examples, logging, properties, etc. The Jaffa
  framework employs some of these strategies.

12
REST Friend or Foe

• REST exhibits more simplicity than the other
  alternatives
• REST offers further decoupling than
  SOAP/WSDL/etc.
• REST potentially violates the SOA contract
  requirements

13
ROA vs. SOA

• My opinion is to strive for a blend
• OASIS SOA-RM A contract represents an
  agreement by two or more parties
• Does the level of abstraction of the contract
  really matter?

14
Why does this matter?

• Adds capability to the SOA
• Further enablement of end-end enterprise
  architecture

15
Platform migration

• Seek a generalized methodology
• Migration strategies are available
• Initially target the low hanging fruit

16
SOA Migration Path
17
SOA Migration Path
18
SOA Migration Path
19
Some Interesting Links

• Web Methods SOA Master Classhttp//www.soamaste
  rclass.com/index.php?optioncom_contenttaskview
  id74Itemid88888964
• Estimate SOA costshttp//weblog.infoworld.com/r
  ealworldsoa/archives/2006/11/how_much_will_y.html
  
• REST FAQhttp//rest.blueoxen.net/cgi-bin/wiki.p
  l?RestFaq
• Two IBM SOA success storieshttp//www.soainacti
  on.com/blog/2007/03/post_4.php
• Web Services Standards posterhttp//www.innoq.c
  om/soa/ws-standards/poster/