ServiceOriented Architecture: Implementation Issues

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

5
Adopting the style

• What kinds of choices tend to result from SOA
  adoption?

Provisioning Models (shared services)
Location Independence (registry)
Controlled vocab
Repositories
SOAP
Agility
WS-
XML
Shared Message Transport
Separation of Business logic (intermediaries)
Event-driven architecture
Standard messages (IEPDs)
Industry Standards
6
Discussion

• Introducing

Kael Goodman GovCore Solutions kael_at_govcore.com 21
2-420-7870
7
Contact Information

• Scott Came
• Director, Systems and Technology
• SEARCH
• scott_at_search.org
• 916-212-5978