1. From Server to Service: How Microsoft moved Team Foundation Server to Windows Azure Grant Holliday Senior Premier Field Engineer AZR323b

5. Demo A quick introduction to http://www.tfspreview.com/ Team Foundation Service

7. James Hamilton

8. The goal should be that a highly-reliable, 24x7 service should be maintained by a small 8x5 operations staff. Engineer the problems. Don’t scale the operations team.

9. Low-cost administration correlates highly with how closely the development, test, and operations teams work together

10. The product team is held accountable for the success of the service. This drives the right behaviours.

11. Brian Harry Version Control Work Item Tracking..Agile Tools Service Delivery Team * Missing a couple of management/organisational layers, but the point is that everybody is on the same team

15. Things to think about Building a Service

17. Error NumberError MessageCause 40197The service has encountered an error processing your request. Please try again. In case of a hardware failure, SQL Database provides automatic failover to optimize availability for your application. Some failover actions may result in an abrupt termination of a session. 40501The service is currently busy. Retry the request after 10 seconds. When soft throttling limit for worker threads on a machine is exceeded, the database with the highest requests per second is throttled. 40552The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction. Uncommitted transactions can block the truncation of log files.

18. Transient Fault Handling Application Block using (SqlConnection conn = new SqlConnection(connString)) { // Attempt to open a connection using the // specified retry policy. conn.OpenWithRetry(retryPolicy); //... execute SQL queries }

19. Transient Fault Handling Application Block using (IDataReader dataReader = selectCommand.ExecuteReaderWithRetry(retryPolicy)) { if (dataReader.Read()) { //... etc

21. ServiceQualifications of Downtime Cloud Services (compute) “Role Instance Downtime” is the total accumulated minutes for all role instances during a billing month that had been deployed and started by action initiated by Customer which had not been running for longer than two minutes without detection and corrective action being initiated. StorageWe guarantee that at least 99.9% of the time we will successfully process correctly formatted requests that we receive to add, update, read and delete data. “Error Rate” is the total number of Failed Storage Transactions divided by the Total Storage Transactions during a set time interval (currently set at one hour). SQL DatabaseSQL Database will maintain a “Monthly Availability” of 99.9% during a billing month. A 5-minute interval is marked as unavailable if all the customer’s attempts to establish a connection to SQL Azure fail or take longer than 30 seconds to succeed, or if all basic valid read and write operations (as described in our technical documentation) fail after connection is established. Exchange Online Any period of time when end users are unable to send or receive email with Outlook Web Access.

31. DNS https://*.tfspreview.com/ VIP 65.52.8.37 Web RoleWorker Role Role Instance #1…n New DNS Record https://sadcustomer.tfspreview.com/ VIP 65.52.X.Y Web Role Role Instance #1 Config DBCustomer DB Attach Debugger

36. Planning for Failure in Cloud Applications (AZR333 - Fri 11:30) Exploring Windows Azure Storage (AZRILL102 - Fri 11:30) Research Paper (http://aka.ms/InternetScaleServices) Exam 70-583: Designing and Developing Windows Azure Applications Find Me Later at the Speaker Lounge (12:45 – 1:45)