The document discusses architecting applications for the cloud using Microsoft technologies. It provides an overview of Microsoft's Azure platform, including hosting applications on Azure infrastructure as a service (IaaS) or platform as a service (PaaS). It also discusses using Azure storage services like tables, queues and blobs to build scalable cloud applications.

1. ArcReady Architecting for the Cloud Phil Wheat Architect Evangelist [email_address] blog: PhilWheat.net

3. Community Events Austin CodeCamp – May 30 th http://www.austincodecamp.com / Dallast TechFest –June 19 th http://www.dallastechfest.com / StartupWeekend San Antonio http ://startupweekend.com/san-antonio-startup-weekend /

4. Are you a technology start-up? BizSpark is an innovative new program that unites Startups with entrepreneurial and technology resources in a global community with a common goal of supporting and accelerating the success of a new generation of high-potential Startups. http://www.microsoft.com/bizspark

5. Microsoft Developer Tools Promotions …ending June 30th, 2009 Contact your local Microsoft Developer Tools Representative for more details… Midwest and North Central Jerry Flynn (314) 872-5919 [email_address] Heartland and South Central Rachel McKane (469) 775-6125 [email_address]

6. ArcReady: Architecting for the cloud

7. About Me Phil Wheat Architect Evangelist [email_address] blog: PhilWheat.net

8. About ArcReady… A forum for aspiring and practicing architects to discuss industry trends An overview of Microsoft’s roadmap as it relates to software architecture A mechanism to solicit your feedback An opportunity to showcase the work you do!

9. Discussion Encouraged

11. SESSION 1 Architecting for the cloud

14. Flashback to previous ArcReady

17. Application Service Providers (ASP)

18. Software as a Service

19. Software + Services

20. “ Packaged” Application An application that I buy “off the shelf” and run myself “ Home Built” Application An application that I develop and run myself Build vs. Buy Build Buy Hosted “ Home Built” An application that I develop myself, but run at a hoster Hosted “ Packaged” An application that I buy “off the shelf” and then run at a hoster “ Home Built” using cloud An application that I develop myself, that is hosted using cloud platform “ Packaged” using cloud An application that I buy “off the shelf”, that is hosted using cloud platform “ Software as a Service” A hosted application that I buy from a vendor “ Platform as a Service” A vendor hosted development and runtime environment On Premise Hoster Cloud Vendor

21. Almost zero upfront infrastructure cost

22. Just in time Infrastructure

23. More efficient resource utilization

24. Usage Based Computing

25. Potential to shrink processing time

26. Concerns with Cloud Computing

27. Security

28. Scalability

29. Reliability

30. Regulations and other legal issues

31. Azure

32. Azure is a blue color on the HSV color wheel at 210 degrees. Azure is the hue that is halfway between blue and cyan. Its complementary color is orange. Azure is a near synonym for the color blue. Commonly it refers to a bright blue, resembling the sky on a bright, clear day. http://en.wikipedia.org/wiki/Azure

34. Platform as a service

35. Your Applications

36. Your Applications

37. Use Case – Erratic Traffic MLB.com is not affiliated with Windows Azure – example only

38. Use Case – Erratic Traffic pgatour.com is not affiliated with Windows Azure – example only

39. Use Case – New Site Launch

40. Web farm that handles request from the internet IIS7 hosted web core Hosts ASP.NET XML based configuration of IIS7 Integrated managed pipeline Supports SSL Windows Azure code access security policy (CAS) for managed code Storage Services Public Internet Web Role Load Balancer

41. No inbound network connections Can read requests from queue in storage Windows Azure specific CAS policy for managed code Storage Service Public Internet Worker Role

42. Public Internet Web Role Storage Service Worker Role Load Balancer

43. Public Internet Web Role Storage Service Worker Role Load Balancer

44. Public Internet Web Role Storage Service Worker Role Load Balancer

45. … Fabric Compute Storage Application Blobs Queues HTTP Tables

46. Storage types: Blobs: a simple hierarchy of binary data Tables: hierarchical storage (not relational tables) Queues: allow message-based communication Access: Data is exposed via a RESTful interface Data can be accessed by: Windows Azure apps Other on-premises or cloud apps

47. Table . . . Table Table Entity . . . Entity Entity Property Property Property Name Type Value Storage Accounts

48. Access via REST You can’t use ordinary ADO.NET No SQL Query language based on the LINQ C# syntax No real joins, aggregates, etc. An unfamiliar hierarchical structure You can’t easily move relational data to it Supporting services are scarce, e.g., reporting There’s significant platform lock-in No schema And no views

49. Massive scalability By effectively allowing scale-out data Highly durable Perspective: Applied to the right problem, Windows Azure Tables are a beautiful thing But they’re not the optimal solution for a majority of data storage scenarios Amazon, Google, and others do quite similar things It appears to be the state of the art for scale-out data

50. What tables don’t do Not relational No Referential Integrity No Joins Limited Queries No Group by No Aggregations No Transactions What tables can do Cheap Very Scalable Flexible Durable If these are important to you, use:

51. Data stored in Tables A Table is a set of Entities (rows) An Entity is a set of Properties (columns) Entity has: PartitionKey – enables scalability RowKey – unique id within the partition (the only indexed property) Timestamp – for optimistic concurrency 255 properties for your data Max size of 1MB

52. Queue Web Role ASP.NET, WCF, etc. Worker Role main() { … } 1) Receive work 2) Put work in queue 3) Get work from queue 4) Do work To scale, add more of either

53. POST http://myaccount. queue .core.windows.net/ myqueue /messages HTTP/1.1 200 OK Transfer-Encoding: chunked Content-Type: application/xml Date: Tue, 09 Dec 2008 21:04:30 GMT Server: Nephos Queue Service Version 1.0 Microsoft-HTTPAPI/2.0  <?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?> <QueueMessagesList> <QueueMessage> <MessageId> 5974b586-0df3-4e2d-ad0c-18e3892bfca2 </MessageId> <InsertionTime> Mon, 22 Sep 2008 23:29:20 GMT </InsertionTime> <ExpirationTime> Mon, 29 Sep 2008 23:29:20 GMT </ExpirationTime> <PopReceipt> YzQ4Yzg1MDIGM0MDFiZDAwYzEw </PopReceipt> <TimeNextVisible> Tue, 23 Sep 2008 05:29:20GMT </TimeNextVisible> <MessageText> PHRlc3Q+dG...dGVzdD4= </MessageText> </QueueMessage> </QueueMessagesList> DELETE http://myaccount. queue .core.windows.net/ myqueue /messages/messageid? popreceipt =YzQ4Yzg1MDIGM0MDFiZDAwYzEw Queue Msg 1 Msg 2 Msg 3 Msg 4 Worker Role Worker Role PutMessage Web Role GetMessage (Timeout) RemoveMessage Msg 2 Msg 1 Worker Role Msg 2

54. Queues guarantee a message will be processed at least once Allows recovery in the event of errors Roles normally consist of several tasks Get Message Insert to Table1 Insert to Table2 Could fail at any point Write your code to expect failures Inserts/Deletes might fail as already performed Data in inconsistent state (part processed)

55. Same tools you’re already used to using, namely Visual Studio Real Storage & Dev Store have differences Fixed schema No dynamic table creating String length nvarchar[1000] – String[64000] Dev Storage forces you to use certain patterns Can be difficult to debug issues in data store: Use logging and tracing Use Fiddler, SQL profiler and SDK docs

57. Your Applications

58. Key developer challenges Many identity providers, many vendors, many protocols, complex semantics – tricky to get right Application strewn with one-off access logic Hard to get right, not agile, not compliant, many dead ends Approach Automate federation for a wide-range of identity providers and technologies Factor the access control logic from the application into manageable collection of rules Easy-to-use framework that ensures correct token processing

59. Key developer challenges Want to easily describe long-running processes Want modularity and nesting Easy to describe but in practice harder to run Hosting and scaling can be challenging Setup and installing, define scale-out approach, ensure long-running availability, manage upgrades, … Approach . NET 3.0/3.5/4.0 addresses key developer requests .NET Services makes it easy to deploy, manage and run Workflows

60. The problem: Exposing internal applications on the Internet isn’t easy Network address translation (NAT) and firewalls get in the way The solution: Service Bus provides a cloud-based intermediary between clients and internal applications It also provides a service registry that clients can use to find the services they need

61. Service Bus Service Bus Registry Endpoints Organization Y Organization X Application Application 2) Discover endpoints 1) Register endpoints 3) Access application

62. Your Applications

63. SQL Services .NET Services Windows Azure Live Services Applications Applications Others Windows Mobile Windows Vista/XP Windows Server SQL Data Services Others (Future)

64. SQL Data Services Data Center Container . . . Container Container HTTP/ SOAP Entity . . . Entity Entity Property Property Property Name Type Value Authorities

65. Resources Jinesh Varia’s Cloud Computing Whitepaper – http://aws.amazon.com Azure Landing Site – http://azure.com Steve Marx - http://blog.smarx.com Azure Team - http://blogs.msdn.com/windowsazure

66. Break

68. SESSION 2 Mesh and Live Services

69. Your Applications

70. Your Applications

71. Windows Live

72. Finished Services

73. Software Applications

74. … are a set of building blocks for handling user data and application resources which can connect your application to hundreds of millions of users. Storage Search & Geospatial Identity Directory Devices Applications Synchronization Mesh Services User Comms & Presence 1.2B 30B 367M 320M nnPB 460M

76. Why Live Services? Engage with over 450M users on Windows Live Integrate with experiences, relationships and data users care about Comprehensive Windows Live services API’s (incl. Messenger, feeds, contacts, search) Developer Tooling with integrated Live Services Open, interoperable programming interface and resource model across digital devices. Data synchronization and local accessibility of web / cloud data Connect across devices Embed social building blocks Jumpstart traffic

77. Virtual Earth

78. Eliminated calls to help center about locations Proof of concept in three weeks 24/7 technical support, easy development with online software development kit Chose Microsoft ® Virtual Earth ™ with the Microsoft MapPoint ® Web service Integrated location information to provide location hours and services Added 3-D maps and integrated driving directions FedEx wanted to increase its visibility and improve customer experience Wanted to add location information and rich features to its online store locater Stable, well-supported solution platform was a must FedEx improves customer experience with integrated mapping and location data “ With Virtual Earth, rather than clicking 10 times to find information, customers get it right away with the compass control.” SNarayanan Kasiarunachalam, Technical Advisor, FedEx Customer Logo

79. Live Mesh

80. Quick Walkthrough and Demo (not nearly as impressive as the video)

83. External Commentary #1 Coolest technology demoed at Web 2.0 “ Live Mesh… could change the way PCs and other devices interact with Internet Services and each other…” “… most ambitious step yet in transforming its personal computer business “ Despite Microsoft’s reputation of being a closed-wall company, it is adopting simple protocols in its Live Mesh synchronization strategy.” “ Live Mesh represents the company Microsoft is trying to become…” Rob Enderle

84. “ Eventually, we’ll give customers instant access to any movie on any device with an Internet connection and a screen.” “More immediately, we could use this technology to reach into airports. Travelers could quickly download movies from Blockbuster kiosks to their portable media players.” Keith Morrow Chief Information Officer, Blockbuster

85. © 2009 Microsoft corporation. all rights reserved. this presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.