Programming AppFabric : Moving Microsoft .NET to the Cloud

1. Required Slide SESSION CODE: ASI308 Programming AppFabric: Moving .NET to the Cloud Programming AppFabric: Moving Microsoft .NET to the Cloud Aaron Skonnard & Keith Brown Cofounders, Pluralsight

2. What is Windows Azure AppFabric? Consists of Service Bus and Access Control

3. Goals of AppFabric • Extend .NET technologies to the cloud • Open and accessible service API • REST, SOAP, RSS, AtomPub, … • Class libraries for .NET, Java, PHP, Ruby, … • Initial focus on two key challenges • Secure connectivity between services • Claims-based access control

4. Service Bus An Internet Service Bus hosted in the Cloud

5. Demo: Quick lap around the Service Bus demo

6. Service Bus • Key developer challenges • Giving business partners secure access to your applications • Characteristics or scale of integration unknown • Users have devices and services running behind firewalls • Approach • Provide a high-scale, high-available “Service Bus” that supports open Internet protocols

7. Service Registry [http|sb]://{account}.servicebus.windows.net/{user-defined} The service registry provides a mapping from URIs to services account svc Root contoso …

8. Demo: Service Registry demo

9. Connectivity • Securely connect applications • Over the internet • Across any network topology • Across organizational boundaries • Primary application patterns • Eventing: notify applications and/or devices • Service Remoting: securely project on-premises services out to the cloud • Tunneling: tunneling TCP protocols through firewalls (e.g. RDP, TDS, etc)

10. Service Bus WCF Bindings

11. Relay Connections Relay http://{account}.servicebus.windows.net/a/b Outbound SSL TCP connection to relay rendezvous endpoint Receiver can also listen over HTTP to overcome port restrictionson the receiving side (“Web sockets”) One-Way Messagesthrough TCP Tunnel Sender Receiver

12. Direct Connections Relay http://{account}.servicebus.windows.net/a/b - Outbound SSL TCP connection to relay - Out-of-band protocol to negotiate Direct Connection Sender Receiver Upgrade to direct connection when possible

13. Eventing: Publish/Subscribe Relay http://{account}.servicebus.windows.net/a/b Outbound SSL TCPconnection to relay rendezvous endpoint One-way messagesthrough TCP Tunnel Sender Receiver Receiver Receiver Receiver

14. Demo: Relay, Direct, and Publish/Subscribe demo

15. Ports required by the Service Bus • 9350 for one-way TCP connections • 9351 for one-way TCP/SSL connections • 9352 for TCP/SSL rendevous (direct) • 9353 for TCP NAT probing (direct) • HTTP uses standard ports (80/443)

16. System connectivity mode • In locked-down network environments, you may need to “listen” via HTTP • System connectivity mode simplifies this process • ServiceBusEnvironment.SystemConnectivity.Mode • This setting applies to all of the “relay” bindings

17. HTTP relay connections • Many of the Service Bus bindings require WCF on the client side • If you want to increase interop, use HTTP • Then the client doesn’t need WCF or the AppFabric SDK • Service Bus provide several HTTP bindings • WebHttpRelayBinding (REST) • BasicHttpRelayBinding (SOAP) • WS2007HttpRelayBinding (SOAP + WS-*)

18. Demo: Exposing HTTP endpoints demo

19. Message buffers • The “relay” bindings require the listener to be present before sending • What if the listener isn’t capable of creating a listener (interop)? • What about scenarios with intermittent connectivity? • This is where message buffers come into play • Message buffers are FIFO queues in the Service Bus that effectively decouple the sender from the receiver • You create message buffers declaratively by posting a “policy” • You program message buffers through a REST API

20. Demo: Programming Message Buffers demo

21. Access Control Controlling who can use your services in the Cloud

22. Access Control • Key developer challenges • Many identity providers, vendors, many protocols, complex semantics – tricky to get right • Applications strewn with one-off authn/authz logic • Hard to get right, not agile, not compliant, ... • Approach • Automate federation for a wide-range of identity providers and technologies through a hosted STS • Model access control logic as rules • Focused on REST services in this release

23. Access Control Access Control is a hosted service that externalizes the authorization policy for federated users Access Control (Hosted Issuer) Trust relationship established Return token Request token Relying Party (Your App) Requestor (Your Customer) Send message with token

24. Rules and claims transformation • AC rules define a claims transformation • Each application can have its own rules • Rules can be chained; e.g. bob  mgr and mgr  allowed • Simple model: the output security token is a collection of claims based on the claims in the incoming token Rules Engine claims in claims out

25. Managing the ACS • Core set of RESTfulmanagement APIs for managing • Issuers and applications • Access control rules • Cryptographic keys • Standards compliant – works with .NET, Java, Ruby, … • Simple Web Token (SWT) • Web Resource Authorization Protocol (WRAP)

26. Demo: The ACS in Action demo

27. Summary • AppFabric extends .NET to the cloud • It's open and accessible • It's easy-to-use your existing .NET skills • It comes with all cloud benefits • Initial focus on two key developer challenges • Secure connectivity between services • Claims-based access control

28. References • AppFabric Developer Portal • http://www.microsoft.com/windowsazure/developers/appfabric/ • Introduction to Windows Azure AppFabric • A Developer’s Guide to the Service Bus • A Developer’s Guide to Access Control • http://www.microsoft.com/windowsazure/whitepapers/

29. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. ASI Track Resources • Website – www.Microsoft.com/WindowsAzure/AppFabric • MSDN Developer Center – http://msdn.microsoft.com/en-us/azure/netservices.aspx • Blog – http://blogs.msdn.com/b/netservices/ • Twitter – http://twitter.com/azure_appfabric • Website – http://www.microsoft.com/biztalk/ • Website – http://msdn.microsoft.com/biztalk/ • Blog – http://blogs.msdn.com/biztalk_server_team_blog • Blog – http://www.biztalkblogs.com/ • Application Infrastructure Virtual Launch Event – www.appinfrastructure.com • AppFabric on Microsoft.com – http://www.microsoft.com/appfabric • Developer Center – http://msdn.microsoft.com/appfabric

30. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

31. Required Slide Complete an evaluation on CommNet and enter to win!

32. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

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

34. Required Slide