1. Connected Systems Architecture
Simon Thurman
Architect
28th February 2005

2. Developer Platform & Evangelism
John Noakes
Platform Strategy Advisor

3. Agenda View of SOA Industry Support Building Services Today
Business Design

4. View of SOA

5. Enterprise Architecture
What it tries to be:
All things to all people
Architectural Blueprint
What should it be:
Strategic Product List?
Governance?
Application Blueprint?
Architectural Principles?

6. The Evolution To Services
Business Benefit
2000+
Web Services
Service-Oriented
Solutions
Late 1990s
Web technologies appear
e.g., HTTP, HTML, XML
Early 1990s
Application integration technologies appear
Pre-1990s
Custom, static
B2B Integration

7. Services Everywhere “Scales Away” spans organizations and geographies
“Scales Out”
by adding machines
“Scales Up” on large systems
“Scales In” on a machine
“Scales Down”
to devices

8. Aligning Business and IT
Top Down
Business Architecture
Operational
Requirements
Functional
Information
Technology
Architecture
Application
Portfolio
Bottom Up IT

9. SOA Definition
- Knowledge about the business
- What are they?
The goal of an SOA is to allow business activities to be orchestrated as components in applications targeting both internal and extra-organizational actors, ultimately enhancing business agility
- Notion of business process
Business and IT alignment: mapping between business activities and components
- Value chains traversal
- Beyond the firewall - Cross “trust boundaries” - Autonomous / Independent actors
- Flexibility
- “Re-wire” as needed

10. What Is Service Orientation?
An approach to building systems using autonomous services which adhere to the 4 tenets of Service Orientation
Boundaries are Explicit
Services are Autonomous
Services share schema and contract, not class
Service compatibility is determined based on policy
Tenet \Ten"et\, n.
Any opinion, principle, dogma, belief, or doctrine, which a person holds or maintains as true Source: Webster's Revised Unabridged Dictionary, © 1996, 1998

11. Service Boundaries Service Boundaries
Platform
Deployment
Trust
Objects are appropriate within boundaries
Services are appropriate across and within boundaries
Service Boundaries Determine Granularity
Subjective – be as granular as you need

12. Three (Compatible) Views of SOA
Solution view
System built from autonomous services
Services are built to last
Systems are built to change
Portfolio view
An approach to factoring and managing an organizational application portfolio
Promotes consistency of information management
And agile solution development
Cross-organizational view
SOA enables structured business collaboration

13. Technical Design

14. Evolving the Abstraction
service models
distributed objects
Abstraction
object models
languages

15. Services  Distributed Objects
Tightly coupled distributed object solution
Service Oriented Architecture
Your
Partner
You
Programming
Language
Programming
Language
Database
Database
Agreements
Object Model
Object Model
Operating
System
Messages
Operating
System
Application
Server
Application
Server

16. Service Orientation Key Concepts
Systems
composed of
Operational
Requirements
enforce
governed by
Policies
Services
Contracts
bound by
have
Messages
exchange
Message Exchange
Pattern
describe
is a set of
define structure of
contain
Schemas

17. Industry Support

18. Web Service Architecture
Metadata &
Discovery
Messaging
Security
Transactions
Orchestration
SOAP and XML
Internet Transports

19. Web Services Interoperability (WSI)
Security WS-Security
WS-Trust
WS-Federation
Reliability WS-Reliable
Messaging
Transactions WS-Transactions
WS-Coordination
WS-AtomicTranscation
WSDL, WS-Policy,
Metadata
WS-Discovery
Messaging SOAP, WS-Addressing, WS-Eventing
XML XML, XSD, XPath
Transports HTTP

20. Building Services Today

21. Application Partitioning (logical)
User Devices
Communication
Operational Management
Security
Users
External Service Agents
UI Components
Presentation
Messaging Infrastructure
UI Process Components
Service Interfaces
Business
Logic
Business Process Components
Business Components
Data
Layer
Business Entities
Data Access Components
Data and
External
Systems
Owned Data Sources
Service Agents
External Services

22. Business Tier – Service Integration
Owned Data Sources
Data Access Components
Service Agents
Service Interfaces
Business Process Components
Business Components
Business Entities
Service Interfaces
Roles:
Expose business functionality through message-based interfaces, enforcing policy
Business Façades, Use Case Facade
Service Agents (Smart Proxies)
Roles:
Invoke external message-based services
Encapsulate policy enforcement for outgoing calls
‘Data Access Components’ for services

23. Multiple Service Interfaces (Multiple Facades)
XML WS Adapter
MSMQ Adapter
Service Interface
XML WS Facade
MSMQ Facade
Abstract Interface (Biz façade)
Biz Component
Expose Business Services (Use Cases)
through several protocols
different authentication model
different SLA

24. Platform Capabilities
Loosely Coupled
Web Services Architecture
Serialization Framework
Asynchronous Communication
MessageQueue Architecture
State Management
Dynamic Type Discovery and Loading
Dynamic Method Invocation
Web Services
Doc Literal
Web Service Enhancements (WSE)
Data Services
Type = XML = Type
Disconnected Model
Dataset
Services
BizTalk
Enterprise Services

25. Further Considerations…
Message Format
Who owns the data and format
Schema Rationalisation, sending makes right, consumer makes right
Reliable Messaging
Fire and Forget
Idempotence
Transactions
ACID or Long Running
Compensation
Service Management
Versioning
Monitoring and Logging
Policy Based Routing
Security
Service Bus
The bit between services
Process Externalisation

26. Business Design

27. Capabilities Map: A Component Model for Business
Enterprise
1. Develop Product / Service
2. Generate Demand
5. Collaboration
3. Fulfill Demand
4. Plan &
Manage
Enterprise
3.1. Provide Service
3.3. Procurement
3.2. Advanced
Planning
3.3.1 Sourcing and Supplier Contract Management
3.3.2 Purchasing
Request Resources
Level 4
3. Fulfill Demand
3.3 Procurement
3.3.2 Purchasing
- Request
Resources
- Create
Purchase
Requisitions
Create
Purchase
Requisitions
3.4. Produce
Product
Receiving of Indirect / Capital Goods and Services
3.5. Logistics

28. Processes: Traversing Capabilities
Suppliers
Customers
Enterprise
Governments
1. Develop
Product /
Service
2. Generate
Demand
5. Collaboration
Channel Partners
3. Fulfill
Demand
4. Plan &
Manage
Enterprise
Logistics
Providers
Financial
Providers

29. Accessing External Capabilities
1. Develop
Product /
Service
2. Generate
Demand
5. Collaboration
3. Fulfill
4. Plan &
Manage
Enterprise
Customers
Logistics
Providers
Financial
Suppliers
Channel Partners
Governments
Partner Capabilities
My Capabilities
Suppliers
Customers
Enterprise
Governments
1. Develop
Product /
Service
2. Generate
Demand
Process Order
5. Collaboration
Channel Partners
3. Fulfill
Demand
3.5.1
Order Fulfillment
4. Plan &
Manage
Enterprise
Shipping
Logistics
Providers
Financial
Providers

30. Conceptual Value Chain
Retailer
Wholesaler
Assembly Manufacturer
Complete
shared
Component Manufacturer
Partial
shared
Logistics Provider

31. Summary A lot of IT Value is in Architecture
Architecture is the key to Agility
SOA Design is NOT an IT-only initiative
SOA Design != distributed computing

32. © 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

33. Backup Slides

34. Service Orientation Compared To Object Orientation
Assume homogeneous platform and execution environment
Share classes, not schemas
Assume cheap, transparent communication
Are linked: Object identity and lifetime maintained by infrastructure
Typically require deployment of both client and server in sync
Are easy to talk about and become a natural path for customers to follow
Customers have 20+ years of experience and great intuition about what “object oriented is”
Service Orientation
Assume heterogeneous platform and execution environment
Share schemas, not classes
Assume variable cost, explicit communication
Are autonomous: Security and failure isolation are a must
Ease “continuous deployment” of client and server separately
Builds on ideas from component software, distributed objects, and MOM
Dominant theme is to manage/reduce sharing between services
Object Orientation is here to stay
Service Orientation offers complementary concepts, not a replacement
Service Orientation will help overcome some Object Orientation limitations and extend the developers abilities across boundaries

35. Web Services Technology Roadmap
Today
Tomorrow
Future
ASMX (aka ASP.NET Web Services)
Windows XP, Server 2003, .NET
Visual Studio 2003
WSE 1.0
Office System 2003
BizTalk Server 2004
SQL Server 2000
ASMX (VS2005 enhancements)
WSE 2.0
Indigo (Beta)
Visual Studio 2005 (Beta)
WSE 3.0 (Tech Preview)
Longhorn (Beta)
Windows Server (Beta)
Indigo
Longhorn
Identity
Windows Server
Federation Server
Visual Studio 2005
WS-I Compliance
SDM
SQL Server 2005

36. Roadmap Provides Continuity
WSE1
WSE2
WSE-n
Indigo will supersede existing connected systems techologies.
Other technologies continue to co-exist, interoperate and be supported via support policy
Indigo
ASMX
ASMX
Enterprise Services
.NET Remoting
Com(+)
MSMQ

37. Integrated Innovation
Integration Across Platforms
Microsoft Integrated Platform
Web Services Integration
Unix
AS400
Linux
OS390

38. WSE v2.0 Features Web Services Security
Digital Signing and Encryption (WS-Security)
Trust Issuing Framework & Secure Conversation (WS-Trust, WS-SecureConversation)
Integration with Windows Authentication and Authorization
X509, Custom Binary, Username/Password, Kerberos, and XML Security Token Support
Roles based authorization with native integration with Windows security
Policy support to describe integrity, confidentiality, and token requirements for communicating with WS endpoints (WS-SecurityPolicy)
Policy driven architecture (WS-Policy)
SOAP Messaging (WS-Addressing)
Message-based programming model
Hosting environment independence
Support for multiple transports (HTTP, TCP)
Content based routing
Attachments
Extensible framework