Current State of Affairs in SOA Along with Migration Strategies and Methodologies 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.MIRO Technologies 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++

PGFSOA n Practical Guide to Federal SOA n Are using OASIS standards such as the SOA Reference Model n Still accepting volunteers

The Standards have Arrived n OASIS SOA RM, SCA, SDO n WS-Transaction n WS-Addressing n Etc.

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

Open Source Contributions n JBoss – jBPM, ESB n Mule ESB n ServiceMix n Synapse

External to Technology n Governance n Methodologies n Management

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

Practices, What Works? n Choose pilots carefully n Governance always comes first n Vendor selection matters even more

Practices, What Works? n SOA as a pattern n Migration strategies n Platform integration

Novel approach – AOP/SOA n Services can be woven rather than orchestrated. n Especially useful for lightweight services with many join points. n Examples, logging, properties, etc. The Jaffa framework employs some of these strategies.

REST – Friend or Foe n REST exhibits more simplicity than the other alternatives n REST offers further decoupling than SOAP/WSDL/etc. n REST potentially violates the SOA contract requirements

ROA vs. SOA n My opinion is to strive for a blend n OASIS SOA-RM: “A contract … represents an agreement by two or more parties” n Does the level of abstraction of the contract really matter?

Why does this matter? n Adds capability to the SOA n Further enablement of end-end enterprise architecture

Platform migration n Seek a generalized methodology n Migration strategies are available n Initially target the “low hanging fruit”

SOA Migration Path

Some Interesting Links n Web Methods SOA Master Class: n Estimate SOA costs: n REST FAQ: n Two IBM SOA success stories: n Web Services Standards poster: