Cloud computing is here to stay, and it is never too soon to begin understanding the impact it will have on application architecture. In this talk we will discuss the two most significant architectural mind-shifts, discussing the key patterns changes generally and seeing how these new cloud patterns map naturally into specific programming practices in Windows Azure. Specifically this relates to (a) Azure Roles and Queues and how to combine them using cloud-friendly design patterns, and (b) the combination of relational data and non-relational data, how to decide among them, and how to combine them. The goal is for mere mortals to build highly reliable applications that scale economically. The concepts discussed in this talk are relevant for developers and architects building systems for the cloud today, or who want to be prepared to move to the cloud in the future. This talk was delivered by Bill Wilder at the Vermont Code Camp 2 on 11-Sept-2010.

2. Cloud-Native Azure Vermont Code Camp 2 11-September-2010 Copyright (c) 2010, Bill Wilder Boston Azure User Group http://bostonazure.org @bostonazure Bill Wilder http://blog.codingoutloud.com @codingoutloud Boston West Toastmasters http://bwtoastmasters.com Not here with my day job Only Bill’s personal views Building Cloud-Native applications using Windows Azure

4. Agenda ? 

5. What is “the cloud”? ?

11. Most $$$ part of Software System?

13. Application Ownership Slide stolen from Chris Bowen’s talk: Windows Azure: What? Why? And a Peek Under the Hood Application Development Network Addressing Network Load Balancing Hardware Repair OS updates & Patches OS Installation Computational Scalability Storage Scalability Hardware Provisioning Staging / Production High Availability Fault Tolerance Data Center Management Stuff We Might Rather Not Deal With Stuff We Like

19. Azure Storage Services in Concert

20. Scaling Out 

21. Web Roles vs. Worker Roles Web Role Worker Role Runs in IIS 7 (always listening) Built using ASP.NET, MVC Good to handle interactive users Addressable over Internet Good for hosting Web API (WCF) Runs Continuously Maps to VM

23. Key Pattern: Roles + Queues Web Role (IIS) Worker Role Queues Blobs Tables

24. Canonical Example: Thumbnails Web Role (IIS) Worker Role Queues Blobs Tables

25. Adding to Queue - Conceptual

26. Adding to Queue - Actual Azure Blob Storage

27. Roles + Queues: API Web Role (IIS) Worker Role Queues queue.AddMessage ( new CloudQueueMessage ( statusUpdateMessage)); CloudQueueMessage statusUpdateMessage = queue.GetMessage ( TimeSpan.FromSeconds(10)); … queue.DeleteMessage ( statusUpdateMessage );

30. Persistent Storage Services – Options Type of Data Traditional Azure Way Relational SQL Server SQL Azure Blob File System, or SQL Server Azure Blobs File File System Azure Drives, or Azure Blobs Reliable Queue MSMQ (maybe) Azure Queues Non-Relational Azure Tables

34. Developer Portal for Keys https://windows.azure.com/

35. Storage Keys for Authentication

42. Azure Table Storage Storage Account Table [*] Entity [*, 1 MB data] PartitionKey + RowKey Property [255x] Name/Value/Type Up to 64k

44. Relational Data vs. Azure Tables Approach SQL Azure Azure Tables Normalization Normalized Denormalized (Duplication) (No duplication) (Lots of duplication) Structure Schema Flexible Transactions Distributed Limited scope Responsibility Database Developer Knobs Many Few Scale Up (or Sharding ) Out Cost Reasonable Very reasonable

45. Replication

54. Geography

57. Not new, but…

58. Accessible to mere mortals Less complex, more cost-effective  competitive pressure … Your competitors are going to be doing it