Slide 2 (Slide 1 skipped)
Is interesting because it shows you continuum of how we’ve moved from on premise to hosted to cloud. At the end of the day it is about saving money. There are some good points here that make sense.
Developers like the cloud because of high level services taking care of coding headaches
The cloud is good because it is so easily scalable and available
Decision makers like the cloud because it is “pay as you go”
Hosted servers are good because you save from buying hardware, compared to on-premise
Hosted does not have as much automation and high level services compared to cloud so you end up having to write more plumbing code.
Defines the entirety of the Windows Azure Platform. This is a great slide because it shows the main pillars in a simple way.
We will focus on Windows Azure and the parts known as “Compute” and “Storage.”
I have already blogged extensively about integrating with SQL Azure.
Slide 5 - 9
Owns all the data center hardware
Uses the inventory to host services
Similar to what a per machine operating system does with applications
Provisions the hardware as necessary
Maintains the health of the hardware
Deploys applications to free resources
Maintains the health of those applications
Fred @ PDC
Worry about having enough machines on hand - Resource allocation
Algorithmicly define how machines are chosen to host services
Responding to hardware failures which will always occur
Procure additional hardware if necessary
IP addresses must be acquired
Load balancers must be programmed
Locate appropriate machines
Update the software/settings as necessary
Only bring down a subset of the service at a time
Maintaining service health
Logging infrastructure is provided to diagnose issues
Slide 10 - Understanding Web Roles and Worker Roles
Blobs, tables, and queues hosted in the cloud, close to your computation
Authenticated access and triple replication to help keep your data safe
Easy access to data with simple REST interfaces, available remotely and from the data center
All access to storage services takes place through the storage account. The storage account is the highest level of the namespace for accessing each of the fundamental services. It is also the basis for authentication.
The Blob service provides storage for entities, such as binary files and text files
Containers and blobs support user-defined metadata in the form of name-value pairs specified as headers on a request operation.
The Queue service provides reliable, persistent messaging within and between services. The REST API for the Queue service exposes two resources: queues and messages
When a message is read from the queue, the consumer is expected to process the message and then delete it. After the message is read, it is made invisible to other consumers for a specified interval. If the message has not yet been deleted at the time the interval expires, its visibility is restored, so that another consumer may process it.
MSDN - The Azure Storage Service API
Storage Explorer Download at CodePlex
Azure ROI Calculator
Slide 16 – SQL Azure
Easy provisioning and deployment
Pay as you go
SLAs and Fault Tolerance
Same code as you’ve always written
Click here for Guidelines and limitations for SQL Azure
No physical admin required
Transact-SQL (T-SQL) support
Integrate existing toolsets
It is just a connection string
Creating, accessing and manipulating tables, views, indexes, roles, stored procedures, triggers, and functions
Execute complex queries and joins across multiple tables
Insert, Update, and Delete
Basic functions (aggregates, math, string, date/time)
Support for tracking billable metrics in real time and for historical analysis
Managed ADO.NET data access
Support for PHP
How about an early preview of upcoming features
The Open Data Protocol (OData) is an emerging standard for querying and updating data over the Web.
OData is a REST-based protocol whose core focus is to maximize the interoperability between data services and clients that wish to access that data.
It is thus being used to expose data from a variety of sources, from relational databases and file systems to content management systems and traditional websites.
In addition, clients across many platforms, ranging from ASP.NET, PHP, and Java websites to Microsoft Excel and applications on mobile devices, are finding it easy to access those vast data stores through OData as well.
SQL Azure Data Sync
Click here to download the Data Sync Framework
Process of synchronizing with the cloud
Tuned for SQL Azure and a stand-alone utility for SQL Server that enables synchronization between an on-premise SQL Server database and SQL Azure
Use the Visual Studio plug-in that demonstrates how to add offline capabilities to applications which synchronize with SQL Azure by using a local SQL Server Compact database
Project “Houston” provides a web-based database management tool for basic database management tasks like authoring and executing queries, designing and editing a database schema, and editing table data.
Navigation pane with object search functionality
Information cube with basic database usage statistics and resource links
Table designer and table data editor
Aided view designer
Aided stored procedure designer
How SQL Azure Works in the Data Center
The Level of Abstraction in SQL Azure Simplifies Coding
Note a few things
Client connects through HTTP, with support for REST
Typically you would use ADO.NET, just as you did with on-premise SQL Server
You just edit web.config to change your connection string
Everything is the same as before (w/ On-Premise SQL Server)
See How to teach cloud computing – The Windows Azure Platform – Step 3 for continuation