This document provides an overview of key concepts for developing applications on the Azure platform, including: - Keeping applications simple and avoiding unnecessary complexity (KISS principle) - Using a loosely coupled architecture with message-based communication like Starbucks' order queue system - Serializing objects when passing messages to increase scalability - Implementing logging and tracing for troubleshooting - Using GUIDs, idempotent operations, and local storage appropriately in the cloud environment - Taking advantage of Azure development tools like the Development Fabric and Storage Explorer.

1. Microsoft Student PartnerAzure Development 101Dominic Green

2. About Me ...

8. Now for the techy stuff...

9. Windows Azure

10. Windows AzureSimplicityKISS – Keep it Simple ...Avoid unnecessary complexity

11. Windows AzureStarbucks ModelOrder taken by one personAdded to a order queueCoffee made by someone elseAllows each worker to specialise

12. Windows AzureLoosely CoupledCashier doesn’t need to know how to make the coffeeMessage based communicationIncreases scalability

13. Windows AzureMessage SerializationCashier writes the order on a cup or ticketAllows complex information passed via queuePassing objects to the queueSerialize – Send – De-Serialize

14. Windows AzureLogging and TracingIf the order goes wrong we should identify where so it doesn't happen to the next customer.Write all activities out to logsCannot attach a debugger to the cloudIdentify cause and location of any problems

15. Windows AzureTrace ManagerTrace In / Out of methodsTrace Extension method for any objectTrace MessageTrace ExceptionEnable tracing from configuration

16. Windows AzureMove away from config filesapp.config and web.config files can no longer be altered normally.Part of the deployed packageUse .cscfg and .csdef filesWorker Role app.config

17. Windows AzureIdentifying MessagesGlobally Unique IdentifierVery low probability of being replicatedTrace message in the cloud

18. Windows AzureAdapt to loadIf too many orders come in everyone should focus on making coffee.Focus on critical operationsTurn features of the site off to ease loadOnce dealt with the spike resume normal service

19. Windows AzureIdempotenceyWe don’t want to make the same order twice, its bad for business.Multiple operations should always give the same result

20. Windows AzureLocal StorageLocal storage can be used as a cacheDon’t store critical dataUse Azure storage to persist dataPlan for the worst

21. Windows AzureDevelopment FabricCan debug applications locally using the development fabricIncluded in the Azure SDKActs as a local cloud

22. Windows AzureDevelopment StorageLocal version of storageRemember to generate your tablesActs slightly different that real storageUse cloud storage as much as possible

23. Windows AzureTable StorageNeed to generate tables locallyEnsure Dev Storage is pointing to the correct tableDifference online

24. Windows AzureProduction and Staging

25. Windows AzureSoftware + ServicesClient applications can use the power of the cloudAdd the endpoints to app.configRich user experienceExtend current applications

26. Windows AzureToolsCloud DriveIncluded in the Windows Azure SDK SamplesWindows Storage Explorerhttp://azurestorageexplorer.codeplex.com/

27. Windows AzureResourcesWindows Azurehttp://blogs.msdn.com/windowsazure/Steve Marxhttp://blogs.smarx.comSriram Krishnanhttp://sriramkrishnan.comCloudy in Seattlehttp://blogs.msdn.com/jnak/

28. @domgreendominic.green@microsoft.comhttp://blogs.msdn.com/domgreenDominic Green