Intro to Windows Azure AppFabric

1. Intro to Windows Azure AppFabric Name Title Microsoft Corporation

2. Session Objectives • What is Windows Azure AppFabric • How is it used? • Billing and Pricing • Environments

3. Challenges Today • How do you integrate with components outside your corporate network? • How do you expose your software to users outside of your organization? • Can they use their existing identities? • What about smaller, non-enterprise customers? • How do you control access to resources that are exposed? • <the list goes on…>

4. Windows Azure AppFabric A natural way to extend the reach of existing services through the cloud • Leverage existing investments in SOA and EAI solutions • Extend the reach of on-premises web services layer • Enable hybrid applications • Security integrate with partners outside of the organizational boundaries

5. About Windows Azure AppFabric • Service Bus • Connectivity across network topologies • Access Control Service • Federated, claims-based authorization for websites and web services

6. Enabling hybrid applications Datacenter Partner LOB app Mobile Device LOB web service

7. Enabling hybrid applications Datacenter Partner ACS LOB app SB Mobile Device LOB web service

8. Enabling hybrid applications Datacenter Partner ACS LOB app SB Mobile Device LOB web service

9. Enabling hybrid applications Datacenter Partner ACS LOB app SB Mobile Device LOB web service

10. Enabling hybrid applications Datacenter Partner ACS LOB app SB Mobile Device LOB web service

11. Service Bus

12. What is it? • Extension to the familiar WCF binding model • SOAP/HTTP • SOAP/TCP • HTTP • Simple HTTP APIs for Service Management • Service Registry (Atom Publishing Protocol) • Message Buffer (REST) • Fully integrated with Access Control Service

13. Service Bus Service Bus • Exchange messages between loosely coupled applications • Network send/receive from any internet connected device • Traverse NAT/Firewall • Message buffering for loosely connected applications • Facilitate direct peer-to-peer connection Send Receive Receive Send App 1 App 2

14. Core Capabilities • Service location and discovery • Simple registry • Access via lightweight ATOM protocols from any platform • Endpoint naming and discovery • Cloud based messaging relay • Allows bridging across NATs and Firewalls • Connect apps without altering the network topology • Network Listen/Send from any Internet-connected device • Standards based HTTP or High Performance TCP • Direct connection functionality using NAT probing

15. Service Bus Patterns • Service Remoting • Extend Services to the Cloud • Eventing • Event Distribution; something happens, you get a notification • Protocol Tunneling • Interconnect applications that are not Web Services

16. Service Remoting Access Control Service Bus Sender Listener • Access Web Services across the Internet • Publish services and communicate bi-directionally

17. Eventing Access Control Service Bus Listener Sender • Notify remote parties of events • Sender transmits information to listeners • Events are distributed unicast or multicast Listener

18. Tunneling Access Control Protocol Bridge Protocol Bridge Service Bus Sender Listener • Transport existing protocols over Service Bus

19. Access Control Service

20. Why an Access Control Service? • Federate identity • Leveraging multiple identity providers per application • ADFS v2, Live ID, Facebook, Yahoo, Google, … • Identity abstraction • Evolve past username/password • Leverage claims-based identity

21. How it works 3. Map input claims to output claims based on access control rules 1. Define access control rules for an identity provider Access Control Service 4. Return token (receive output claims) 0. Establish trust via key exchange 2. Request token (pass input claims) 6. Process token Your Service Customer 5. Send message with token

22. Capabilities • ACS == claims-based access control • Key features • Open to all platforms • Simple rules for mapping input to output claims • OAuth WRAP & SWT • Integrates with ADFS v2 • All web services can take advantage of these capabilities with a single code base

23. Pricing & Environments

24. Billing and Pricing • Service Bus • Individual @ $3.99 per connection-month • Pack-based @ $1.99 per connection-month • Access Control • Consumption @ $1.99 per 100k transactions • Bandwidth • Same as Windows Azure

25. Environments • Production • Paying customers, support, SLAs • 3 month release cadence • <your-namespace>.servicebus.windows.net • Geo-located • Labs • Free, no support, no SLA • ~3 month release cadence • <your-namespace>.servicebus.appfabriclabs.com • Available for evaluation and prototyping

26. Takeaways • AppFabric provides a natural way to extend the reach of existing services through the cloud • Service Bus provides a topology agnostic message bus in the cloud • Access Control Service removes complex authentication and authorization rules from your application

27. © 2010 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.