 Clemens Vasters Service Bus Technical Lead Microsoft Corporation BB38

Service Orchestration Service Orchestration Service Registry Naming Federated Identity and Access Control Messaging Fabric CRMCRM Customers Leads Trends Campaigns Supply Chain Inventory Order Entry Planning Purchasing Point Of Sale POS Integration Product Catalog Returns Web Store

Service Orchestration Service Orchestration Service Registry Naming Federated Identity and Access Control Messaging Fabric ClientsClients MS/3 rd Party Services MS/3 rd Party Services On-Premise ESB ESBESB Desktop, RIA, Web Desktop, RIA, & Web Your Services

Sender Receiver ? Machine Firewall Network Firewall Network Address Translation Dynamic IP

Sender Receiver ? Machine Firewall Network Firewall Network Address Translation Dynamic IP Brittle, Difficult, Insecure – and sometimes – Impractical Consequence: We see recurring patterns of workarounds

Service Registry Naming Federated Identity and Access Control Messaging Fabric

Root Solution NameB NameC Name1 Name2 Name3 NameA

Root X Y Z B C A

SBWNservices solution name Required Prefix

Root Solution NameB NameC Name1 Name2 Name3 NameA

Service Registry Naming Federated Identity and Access Control Messaging Fabric

Naming Service Registry Client AtomPub WS-Transfer

Naming Root SBWNservices svc solutionsvc solution Client AtomPub WS-Transfer

 Clemens Vasters Service Bus Technical Lead.NET Services

Title urn:uuid:82a76c80-d498-12d5-b91C e0ef6 … MyEndpoint urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a

Service Registry Naming Federated Identity and Access Control Messaging Fabric

Service Bus Sender Receiver sb://servicebus.windows.net/services/solution/a/b/ outbound connect one-way net.tcp TCP/SSL 828 Backend Naming Routing Fabric Frontend Nodes TCP/SSL 808/828 outbound connect bidi socket Msg NAT Firewall Dynamic IP Subscribe Route NLB

 Clemens Vasters Service Bus Technical Lead.NET Services

Service Bus Sender Receiver sb://servicebus.windows.net/services/solution/a/b/ outbound connect bidi socket outbound connect one-way net.tcp TCP/SSL 828 Backend Naming Routing Fabric Frontend Nodes TCP/SSL 808/828 Msg Subscribe Route Receiver outbound connect bidi socket TCP/SSL 828 Msg

 Clemens Vasters Service Bus Technical Lead.NET Services

Service Bus Sender Receiver sb://servicebus.windows.net/services/solution/a/b/ Backend Naming Routing Fabric Frontend Nodes Ctrl Socket-Socket Forwarder outbound socket connect outbound socket rendezvous Ctrl TCP/SSL 818 Oneway Rendezvous Ctrl Msg Oneway Rendezvous Ctrl Msg NLB

 Clemens Vasters Service Bus Technical Lead.NET Services

Service Bus Sender Receiver sb://servicebus.windows.net/services/solution/a/b/ Backend Naming Routing Fabric Frontend Nodes Ctrl relayed connect Oneway Rendezvous Ctrl Msg Oneway Rendezvous Ctrl Msg relayed rendezvous TCP/SSL 818, 819 NAT Probing NAT Traversal Connection upgrade

 Clemens Vasters Service Bus Technical Lead.NET Services

Service Bus Sender Receiver sb://servicebus.windows.net/services/solution/a/b/ Backend Naming Routing Fabric Frontend Nodes Ctrl HTTP-Socket Forwarder HTTP HTTPS request outbound socket rendezvous Ctrl HTTP/S 80/443 Oneway Rendezvous Ctrl Msg Oneway Rendezvous Ctrl Msg NLB

 Clemens Vasters Service Bus Technical Lead.NET Services

Service Registry Naming Federated Identity and Access Control Messaging Fabric

Receiver Access Control STS Service Bus Relay RST/RSTR Ac Tk Token Header Ac Tk #Listen Acquire Access Token #Listen Pass Access Token with Subscription Token Evaluated 3 3

Receiver Sender Access Control STS RST/RSTR Service Bus Relay Ac Tk Token Header Ac Tk #Send Acquire Access Token #Send Pass Access Token with Message Token Evaluated and Removed Message Passed on to Receiver

Please fill out your evaluation for this session at: This session will be available as a recording at:

© 2008 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.