1. Service-Oriented Architecture: Implementation Issues
Regional Information Sharing Conference
San Diego, CA
November 29, 2006
Scott Came
SEARCH Director of Systems and Technology

2. Recap of Yesterday
SOA is an architectural style to guide the design of information sharing and integration solutions
Architects select it when agility is a primary desired characteristic
Agility is about handling changes in context with minimal cost

3. SOA Implementation
So, if SOA is the right style for your information sharing architecture, how do you “do” it?

4. What SOA is Not The same as web services
Service buses and message brokers
An infrastructure investment strategy
The brainchild of any particular vendor
Practically speaking, all these issues play a role in implementing SOA
SOA is not web services, but web services can be an effective means of implementing an SOA
SOA is not about classes of tools, though tools can be useful as part of an implementation strategy
SOA is not going to tell you who provisions what, where to outsource, what to share

5. Adopting the style
What kinds of choices tend to result from SOA adoption?
(shared services)
Provisioning
Models
Independence
Location
(registry)
Controlled vocab
Repositories
SOAP
XML
WS-*
Agility
Emphasize that SOA is not primarily about implementing particular infrastructure…it’s more about adopting a philosophy to guide your information sharing and integration architecture/approach. Thus the proper way to talk about SOA implementation is the kinds of implementation choices that result from adopting the style.
Also discuss how SOA adoption is the iterative pursuit of a continuum. There are things you can do to “tend towards” the style without doing it all.
Infrastructure investment (and investment strategy) depends on where you are on the continuum. Each step also introduces additional governance issues, skills needs, risks, etc.
Message
Shared
Transport
Separation of
Business logic
(intermediaries)
Event-driven
architecture
Standard messages
(IEPDs)
Industry Standards

6. Discussion Introducing: Kael Goodman GovCore Solutions

7. Director, Systems and Technology
Contact Information
Scott Came
Director, Systems and Technology
SEARCH