1. Benjamin Day www.benday.com blog.benday.com

2.  Owner, Benjamin Day Consulting, Inc.  Email: benday@benday.combenday@benday.com  Web: http://www.benday.comhttp://www.benday.com  Blog: http://blog.benday.comhttp://blog.benday.com  Trainer, Consultant  Visual Studio Team System, Team Foundation Server  Microsoft MVP for VSTS  Microsoft VSTS/TFS Customer Advisory Council  Microsoft Cloud Services Advisory Group  Leader of Beantown.NET INETA User Group

7.  Think data-center somewhere on the internet  Allows you to run your app  Allows you to read and write data

8.  Microsoft’s “cloud”  Every cloud has an Azure lining?  Custom version of Windows  Optimized for utility computing applications  Always runs virtualized on the Azure Fabric  Azure Fabric  Runs instances of your apps  Handles “everything”  Azure Storage  Azure SDK for Visual Studio

9.  “I’ve got my awesome data-center so…”  No more worrying about…  Buying, configuring, maintaining hardware  Buying, configuring, maintaining the operating system  Network infrastructure ▪ Routers, Switches, Load Balancers  Your data-center’s power and internet connections  Failovers  Worry less about…  App deployment  Capacity planning  Focus on writing your app

11.  Developing a service  Testing and debugging locally  Deploying to the cloud  Maintaining a running service

13.  Visual Studio  Templates  Debugging .NET platform .NET, IIS7, WCF  “The cloud on your desktop”  Complete offline cloud simulation  Like Cassini (web development server)

15. Default.aspx

16.  Scalability  Availability  Zero-downtime upgrades  All with existing tools and skills Default.aspx LB

17. What about state? (e.g., shopping cart)

18. Durable Store

20.  Durable, scalable, available store  Simple abstractions  Simple interface  REST  ADO.NET Data Services Blobs Tables … … Queues

21.  Simple database in the cloud  You don’t worry about replication  Highly scalable  Development version  DevelopmentStorage.exe  Uses SQL Server Express

23.  Every row has RowKey & Partition Key  RowKey = primary key  PartitionKey  Helps you tell Azure how to scale your data  You have to think about how you’ll be querying  By State? By Hour? Other? RowKeyPartitionKeyFirstNameLastName 1MABenDay 2MAJohnMalkovich 3WABillGates 4CASteveJobs

24.  Your partitions could be on different servers  Best practice: If you know your PartitionKey, add it to the WHERE clause  No PartitionKey in the WHERE  insane table scans  Recommendation: More partitions is (probably) better

25.  Partition key and Row key  String (up to 64KB)  Other properties  String (up to 64KB)  Binary (up to 64KB)  Bool  DateTime  GUID  Int  Int64  Double

26.  No foreign keys  No triggers  No stored procedures  In Table storage, strings can only be 64k  You’ll need to use a mix of Blob and Tables  Think hard about what config values you put in web.config/app.config vs ServiceConfiguration.cscfg

27. Default.aspx Storage (Blobs, Tables, Queues) LB

28.  Cloud services aren’t just websites  Many other types of work for the cloud  Bulk file conversion  Heavy analytics  Finding extraterrestrials  Even websites can offload async work  We need a more complex architecture

29. Storage LB Worker.cs

30. Default.aspx Storage LB

31. Storage LBLB LBLB

33. Default.aspx Storage (Blobs, Tables, Queues) LBLB LBLB

34. Default.aspx Storage (Blobs, Tables, Queues) LBLB LBLB Worker.cs Simple queue interface

36.  Remember, no surprises  Offline, just what you would expect  Set breakpoints  Step into code  Inspect variables  What about in the cloud?

37.  We can debug a service in Visual Studio  How do you debug a service that has been deployed?  Answer: you don’t  Logging is the answer  RoleManager.WriteToLog(eventLogName, message)  Event log name values: Error, Information, Warning, Debug, Critical

38.  Debugging the cloud really means logging  Simple logging API today  More functionality over time

40. 1. Write code on your laptop 2. Upload your package to the web portal 3. Push “deploy” 4. Monitor, upgrade, scale…

42.  Familiar development  Local debugging  Simple deployment  Automated management

43.  My Blog  http://blog.benday.com http://blog.benday.com  Sample code  More Azure content to come…  Steve Marx’s blog  http://blog.smarx.com/ http://blog.smarx.com/  Evangelist for the Azure team  Azure.com

44.  Go to http://azure.comhttp://azure.com  Download the SDK, write some code  Watch these talks on PDC 2008 Website:  Storage (Brad Calder)  Best Practices (Sriram Krishnan)  Programming Model (Daniel Wang)

45. Thanks for the photos! Developer desk: http://www.flickr.com/photos/dunkv/97119622/ http://www.flickr.com/photos/dunkv/97119622/ Concrete, WA: http://flickr.com/photos/karynsig/771785316/ http://flickr.com/photos/karynsig/771785316/

47.  Robot Pack - Lego NXT Robot Kit + WROX Robotics Developer Studio book  Mobility Pack - LifeCam NX-6000 & Wireless Notebook Laser Mouse 6000  Gamer Pack - Gears of War 2, PGR4, Mass Effect, Xbox 360 Wireless Headset & 3-month XBOX Live Card  MSDN Subscription - one-year VSTS 2008 Team Suite w/MSDN Premium Subscription  SoftLayer: Free WS 2008 Web Edition and SQL Web Edition with any server order over $179 + Giveaways will happen at the end of the last session in each breakout room. You must fill out page 1 completely and you must be present to win.

48.  Owner, Benjamin Day Consulting, Inc.  Email: benday@benday.combenday@benday.com  Web: http://www.benday.comhttp://www.benday.com  Blog: http://blog.benday.comhttp://blog.benday.com  Trainer, Consultant  Visual Studio Team System, Team Foundation Server  Microsoft MVP for VSTS  Microsoft VSTS/TFS Customer Advisory Council  Microsoft Cloud Services Advisory Group  Leader of Beantown.NET INETA User Group

49. © 2008 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.