what is soa?
DESCRIPTION
This is a brief taster presentation in to the Service Oriented Architecture which I prepared for my company as part of job handover. I used it sow seeds of SOA and hopefully people took away a sense of how can we be more SOA like, even if switching completely to SOA would be a step too far. Feel free to use.TRANSCRIPT
What is SOA?
Scott Bown
This presentation
SOA Taster Basic concepts allowing completion
of your SOA personal objective Time for discussion Not a in-depth detailed explanation Not how to deploy at this company
Summary
What is SOA? What is a Service? Key Principles Governance and ESB XML Web services Where next?
Service-Oriented Architecture
Not a technology or a product There’s no install file Not Java/C/RPG/Groovy etc
It’s a style of design: Architecture Methodology Organisation
What’s a service?
"A service is a discoverable resource that executes a repeatable task, and is described by an externalized service specification.“
Business alignment Specifications Reusability Agreements Hosting and discoverability Aggregation
Key Principles of SOA
Explicit Boundaries Shared Contract and Schema Interoperability Loose coupling Reuse Language/Vendor agnostic
Governance
Managing the portfolio of services
Managing the service lifecycle
Using policies to restrict behavior
Monitoring performance
Enterprise Service Bus (ESB)
Artifact Store
Like the common libraries database but for services
Meta information about the services How to use them What they do Business contacts
Technology: XML
Open document based standard for standardised information interchange
Human readable Example:
<dept id=“IT”><employee id=“123”>
<name>Scott</name></employee>
</dept>
Technology: WebServices
Fit some of the SOA ideals Programming
language agnostic Contracts between
services Discoverable services Standardised
specifications
Is using web services using SOA?
A: ??
Are we currently using SOA principles?
A. ??
Key things to take away
SOA is a way of architecture Services - Cohesive pieces of
functionality that are autonomous Artifact store – stores service details
so you can reuse EBS – connects everything together Governance – control and
monitoring
What next?
Learn and use XML Learn and use Web services Create services (programs) that are
autonomous and loosely coupled
Resources
www.ibm.com/software/solutions/soa www.eclipse.org/swordfish Google: SOA [Don’t do an image search ‘soa’]
IBM DevWorks XML/WS tutorials and free ebooks