1. The Windows Communication Foundation
Next Generation Business Solutions Platform Strategy Review
11/29/ :01 AM
Story:
We’ve never had so much connectivity – most people have affordable access to some form of internet connection and many of those have broadband – I have 6Mb into my house!
Risman Adnan ISV Lead, Microsoft Indonesia
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. From Objects to Services
Next Generation Business Solutions Platform Strategy Review
11/29/ :01 AM
Object-Oriented
1980s
Polymorphism
Encapsulation
Subclassing
Speaker Notes
For years, software development has focused on how to best reuse the code that we write. Ultimately, people and businesses want long-term return on their short-term investments in code. How do we do this?
We’ve seen 3 waves of advancement in this movement in recent decades:
1980s and Object-Orientation: Object-oriented development promised the idea of building reusable abstractions (called classes) that we could then inherit from in order to reuse the base class functionality. This shift from simple procedural-based code brought with it a lot of benefits including polymorphism (the ability to dynamically bind types at runtime), abstractions that included both state and behavior, and encapsulation (controlling which parts of the code the external world can access). However, Object-Orientation by itself didn’t facilitate the dynamic evolution of software at runtime. Once an application was built, it was static. There wasn’t an easy way to infuse new code into an application.
1990s and Components: Component-based development helped us overcome this challenge. It forced the developer to think about the external facing interface of the application. This enabled us to build systems that dynamically load and bind to new functionality at runtime (an application discovers new components after it has been built) and introduced the notion of an application as a growing/evolving organism. To facilitate dynamic loading, we saw a big emphasis on runtime metadata. In the past, you couldn’t easily discern application capabilities since there was very little/rudimentary metadata information stored as part of the application. Whereas C and C++ programs from 1980s were these relatively opaque collections of code, component-based applications of the 1990s enabled runtime inspection of code to determine what a particular component supported. This introduced the notion of self-describing systems. But while this metaphor worked really well on a single machine (using method invocation on an object reference), we hit scaling problems when we tried to stretch it out and apply it as the substrate for distributed software integration (across machines, etc).
2000s and Service-Orientation – With Service-Orientation, we retain the benefits of self-describing applications, explicit encapsulation, and dynamic loading of functionality. What changes is the metaphor with which we accomplish it. Instead of using method invocation on an object reference, we shift the conversation to that of message passing – a proven metaphor for scalable distributed software integration. In addition, to support dynamic loading of service-based functionality, we use schema to describes the structure of messages, behavioral contract to define acceptable message exchange patterns, and policy to define service semantics.
Simplifying service-oriented development is one of the biggest bets we’re making in "WCF". "WCF" takes the service-oriented concepts of message passing, schema, contract, and policy, and implicitly applies it to all of the services we build. As such, "WCF" provides you with the first true service-oriented programming model.
Transition to next slide:
We define service oriented applications as those that adhere to “The Four Tenets of Service-Orientation.” Let’s examine these and see how "WCF" implements them…
Component-Oriented
1990s
Location Transparent
Tight Coupling
Runtime Metadata
Service-Oriented
2000s
Message-based
Schema+Contract+Policy
Broad Interop
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

3. Service Orientation? SOA … what does it really mean?
Service Orientation is the recommended paradigm for delivering distributed systems
SO is not a technology
SO does not require or mandate WS
BUT WS are closely aligned to SO
SO is about EVOLUTION
Does not require massive learning exercise
Delivers value from what you already know
Apply existing design principles but apply a set of Four Tenets …

4. Architecture Programming Model
Client
Service A B C Bv Bv Bv A B C
Message A B C Bv
Address
Binding
Contract
(Where)
(How)
(What)
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

5. Architecture Layering
11/29/ :01 AM
Architecture Layering
Service A B C Bv A B C Bv
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

6. Architecture: Description & Runtime
11/29/ :01 AM
Architecture: Description & Runtime
Client
Service A B C Bv Bv Bv A B C
Message A B C Bv
ChannelFactory<T>
ServiceHost
Description
Runtime
Description
Runtime
©2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

7. Next Generation Business Solutions Platform Strategy Review
11/29/ :01 AM
WCF extends the .NET Framework
Services are built in Visual Studio 2005 using any .NET programming language
Intelligent code editing
Debugging
Deployment
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

8. Next Generation Business Solutions Platform Strategy Review
WS-* Protocol Support
Next Generation Business Solutions Platform Strategy Review
11/29/ :01 AM
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

9. WS-* Spec Status WS-BPEL WS-Federation WS-Management Devices Profile
Step 2 – Workshops & Community Dev
Business Process
Step 3 – Standardization
WS-BPEL
Step 4 – Approved Standard
Infrastructure
and Profiles
Metadata
WS-Federation
WS-Management
Devices
Profile
WS-Metadata
Exchange
Assurances
WS-Secure
Conversation
WS-Business
Activity
WS-Discovery
WS-Trust
WS-Atomic
Transaction
UDDI
WS-Security
WS-Reliable
Messaging
WS-Coordination
WS-Policy
Messaging
WS-Transfer
WS-Enumeration
WS-Eventing
WSDL
SOAP
WS-Addressing
MTOM
XML Schema
Foundation
XML Infoset
SOAP / UDP
XML 1.0
XML
Namespaces
MIME
SOAP / HTTP

10. WS-* Protocols - Industry Adoption
WS-RM
WS-AT
WS-D
DPWS
Devices
SOAP/WSDL
Assurances
WS-SecureConv
MTOM
BEA Systems Inc. A
Brother Industries 
Canon Inc.
Epson Corp.
Exceptional Innovation
Fuji-Xerox Co.
gSOAP ü HP
Intel Corp.
Lexmark International, Inc.
Microsoft
Peerless Systems Corp.
Schneider Electric SA
Toshiba
WebMethods Inc.
Xerox Corp.
Messaging
Apache (WSO2) ü
BEA Systems Inc. A
Choreology Ltd
IBM Corp.
IONA Technologies
JBoss Inc. (Arjuna)
Mercury (Systinet)
Microsoft
Oracle 
SAP
Sonic Software
Sun Microsystems Inc.
Tibco Software, Inc.
WS-Security
WS-Trust
WS-Fed
Apache (WSO2) ü
Amazon
BEA Systems Inc. 
Cape Clear Software Inc.
Canon Inc.
eBay Inc.
Epson Corp.
Fuji-Xerox
Google
gSOAP HP
IBM Corp.
Intel Corp.
Iona
JBoss Inc.
Microsoft
Novell
Oracle
Ricoh Co.
SAP
Sun Microsystems, Inc.
Xerox Corp.
Security
Apache (WSO2) ü 
BEA Systems Inc. A
BMC (OpenNetwork)
Canon Inc.
Cape Clear Software Inc.
Computer Associates (Netegrity)
gSOAP
IBM Corp. (DataPower)
IONA Technologies
JBoss Inc.
Layer 7 Technologies Inc.
Mercury (Systinet)
Microsoft
Nokia
Novell
Oracle
RSA Security Inc.
Ping Identity Corp.
SAP
Sonic Software
Sun Microsystems, Inc.
Tibco Software, Inc.
Verisign Inc
WebMethods Inc.
Metadata
MEX
WS-P
UDDI
Apache (WSO2) ü
BEA Systems Inc. 
Computer Associates A
gSOAP
IBM Corp.
JBoss Inc.
Layer 7 Technologies
Mercury (Systinet)
Microsoft
Novell
Oracle
SAP
Sun Microsystems, Inc.
Sonic Software
WebMethods Inc.
WS-XFer / Enum
WS-Man
System Mgmt
AMD Inc. A
Computer Associates
Dell Inc. 
gSOAP ü
Intel Corp.
Mercury (Systinet)
Microsoft
Oracle
SAP
Sonic Software
Sun Microsystems, Inc.
WEBM Solutions, Inc. ü
Released Product 
Public Interop A
Co-Author Only
© Microsoft Corporation. All rights reserved. The information contained in
this document represents the current view at the time of publication and is subject to change.

11. SOA is Composed of Multiple Layers
Oracle
SAP
SQL
Compass I2
Presentation Layer :
Portals ,
Web Apps
Mobile Apps
&
Thick Clients
Orchestration Layer
Composite Applications
BPM and Workflow
Integration Layer
EII
EAI and Web Services
Data Layer
Systems of Record
Enterprise Applications and Data Systems
Business Logic Layer
Web Services -
based Business Objects
SOA
Fabric
Service-Orientation Principles
Coarse-grained, self-describing, business services:
Share a formal contract
Are loosely coupled
Abstract underlying logic
Are composable
Are reusable
Are autonomous
Are stateless
Are discoverable

12. ESB Architecture Approach
ESB Client Software
Installed on every node
Transport and repository
Transformation Service
Routing Service
ESB Client Software
Installed on every node
.NET Application
J2EE Application
Web Service Endpoint

13. Microsoft ESB Guidance
Service-Oriented Infrastructure
Supported Service Provider
Native
Supported Service Consumer
Native
Enterprise Service Bus
ESB Core Engine
Transformation
Routing
Exception Management
Orchestration
Adaptation
B2B Gateway
Provisioning Framework
Standard Service Consumer
SOAP
Standard Service Provider
SOAP
WCF
WCF
CIM
SIM
Service Registry
Service Management
Security
Legend:
CIM Consumer Integration Module
SIM Service Integration Module

14. Business Intelligence Development and Tooling Workflow Orchestration
11/29/ :01 AM
User Experience
Composite Apps
OBA/Office
Devices
Web
Portal
Collaboration
Business Intelligence
Development and Tooling
Identity & Access
Management
Composition Layer
Data Aggregation
Workflow Orchestration
Eventing
Service Agents
Business Rules
Data Platform
Data Management
Data Integration
Applications
ERP
SCM
CICS
CRM
Core Infrastructure
Application Server
11/29/2018
© Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

15. “Real World” Applications
Office Business Applications
Estimate custom design
Unstructured
Word
Excel
Outlook
InfoPath
Get specs from customer
Validate specs with Tech Sales
Office SharePoint Server
Estimate custom design
Unstructured
Cost out the solution
Decide discount strategy
Assemble proposed response
Approve proposed response
SOA Business Processes
Create
Lead
Create
Oppt’y
Create
Quote
Complete
Sale
Create Invoice
Qualified?
Closed?
Retire
Lead
Structured 15 15

16. SOA Infrastructure Lifecycle Service Management Notifications
11/29/ :01 AM
SOA Infrastructure
Lifecycle
Service Management
Infrastructure
Notifications
Asset Mgmt
Portfolio Mgmt
Configuration Mgmt
Service Repository
Enterprise Reporting
Exception Mgmt
Root Cause Analysis
Notification Services
Reporting
Auditing, Logging, Quality of Service, Performance Monitoring, Availability
Service Monitoring
Capability Repository
Discovery
Contact
Publish
Billing
Subscription
Rating
Stage Management
Provisioning
Dependency Analysis
Data Contract, Message Contract, Policy, Model
Service Versioning
Identity
MICROSOFT CONFIDENTIAL
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. Next Generation Business Solutions Platform Strategy Review
11/29/ :01 AM
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.