Nick harris-sic-2011

Nick Harris
Technical Evangelist
@cloudnick
http://www.nickharris.net

Agenda
• This session is focused on building device
applications with Windows Azure
• We’ll talk about storage, identity,
communications, platform services, and
tools
• A couple demos

demo
BabelCam
Windows Phone application leveraging
Windows Azure

Any pictures?
WAZ
SAS Storage
Process Image

Windows Azure
Store Image in Windows
Shared Access
Access Token
Authenticate
User Authentication
Send Notification
Process Image
Signature
Azure Blob Storage

Translated Text
Send Image

Translated
Translated Text
Text

Microsoft Push
Hawaii OCR &
Notification
Bing Translator
Service

What did we just see?
• Storage
• Identity
• Communications
• Platform Services

Why Device + Cloud?
• The cloud levels the playing
field
• The cloud provides a larger
pool of resources from
which to pull
• The cloud provides a way
to reach across device
platforms

Why Windows Azure?
• PaaS: you built it, Windows Azure runs it
• Automatic O/S patching
• Elasticity and scale
• Utility billing
• Higher-level services
– ACS, Traffic Manager, Caching, CDN

Storage: What are our options?
• Windows Azure Tables
– Non-relational structured storage
– Massive scale-out
• Windows Azure Blobs
– Big files
• Windows Azure Queues
– Persistent Async Messaging
– Enqueue, Dequeue

Storage: What are our options?
• SQL Azure
– Relational database
– Highly available
– Managed for you as a service

Storage: Secrets

• Windows Azure
– Storage name
– Storage key
• SQL Azure
– Username
– Password
Once your share your secret, it’s no longer secret

Storage: How do we keep secrets secret?
Proxy the requests (2)

Web
1. Client sends data to Role
web role
2. Web role sends data to
storage (1)

Storage: Using Shared Access
Signatures
• Client makes request
of Web Role for SAS Web
• Web Role sends Role (3) (4)

client SAS (2)

• Client makes request (1)
• Client gets response

Storage: SQL Azure
• Client sends request (2)
to proxy
• Proxy makes SQL call Web (3)
Role
against SQL Azure
• SQL Azure returns a (4)
response
• Proxy returns (1)
response to device

Storage: Offloading work through queues
• Client writes a Worker
(2)
message to a queue Role
(3)
• Worker role is polling
the queue
• Worker role finds the (1)
message

Identity: What are the options?
• Create your own
– Username + password, token, etc.
– ASP.NET Membership Providers
• Use a single existing identity system
– Live Id, Facebook, etc.
– Develop directly against IdP protocol
• Outsource identity management
– Access Control Service

Communications
• Two forms of communication with devices
– Device-initiated
– Cloud-initiated

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>

<id>http://localhost:33779/WcfDataSer vice1.sv c/Drive rs</id>
<updated>2010-05-24T22:12:38Z</upda ted>
<link rel="self" title="Drivers" href="Drivers" />
- <entry>
<id>http://localhost:33779/WcfDataSer vice1.sv c/Drive rs(1)</id>
Communications: Device-initiated
- <feed xml:base="http://localhost:3377 9/Wcf DataSer vice1.svc/" xmlns:d="http://schemas.microsoft.com/ado/2007/08 /datas ervices" xmlns:m="http://schemas.microsof t.com/ado/20 07/08/dataserv ices/m etadata "
xmlns="http://www.w3.org/2005/Atom">
<title type="text">Drivers</title>
<ArrayOfDriver xmlns=http://schemas.datacontract.org/2004/07/ContosoWcfService.Models
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<title type="text" />

<Driver>
- <author>
<name />
</author>
<link rel="edit" title="Driver" href="Drivers(1)" />
<link rel="http://schemas.microsoft.com/ado/2007/08 /dataservices/related/DistributionCenter" type="application/atom+xml;type=e ntry" title="DistributionCenter" href="Drivers(1)/DistributionCenter" />

• Device-initiated options
<DistributionCenterId>1</DistributionCenterId>
<link rel="http://schemas.microsoft.com/ado/2007/08 /dataservices/related/Today s" type="application/atom+xml;type=feed" title="Todays" href="Drivers(1)/Todays" />
<category term="ContosoBottlingMode l.Driver " scheme="http://schemas.microsof t.com/ado/20 07/08/dataserv ices/scheme" />
- <content type="application/xml">
- <m:properties>
<d:DriverId m:type="Edm.Int32">1</d:DriverI d>

<DriverId>1</DriverId>
<d:DistributionCenterId m:type="Edm.Int32">1</d:Distributi onCente rId>
<d:FirstName>Rob</d:FirstName>
<d:LastName>Tiffany</d:LastName>
</m:properties>
</content>

<FirstName>Rob</FirstName>
</entry>
- <entry>

<LastName>Tiffany</LastName>
- <author>
<name />
</author>

</Driver>
- <m:properties>

<Driver>
<d:FirstName>Loke Uei</d:FirstName>
<d:LastName>Tan</d:LastName>
</m:properties>
</content>

</entry>
- <entry>

- <author>
<name />
</author>

– HTTP-based, request/response

<FirstName>Loke Uei</FirstName>
- <m:properties>

<LastName>Tan</LastName>
<d:FirstName>Dan</d:FirstName>
<d:LastName>Bouie</d:LastName>
</m:properties>
</content>

</Driver>
</entry>
- <entry>

<Driver>
- <author>
<name />
</author>

- <m:properties>

<d:FirstName>John</d:FirstName>
<d:LastName>Dietz</d:LastName>
</m:properties>
</content>

<FirstName>Dan</FirstName>
</entry>

[{"DistributionCenterId":1,"DriverId":1,"FirstName":"Rob","LastName":"Tiffany"},
- <entry>

– Framework choices (WCF, OData,
<LastName>Bouie</LastName>
- <author>
<name />
</author>

</Driver>

{"DistributionCenterId":1,"DriverId":2,"FirstName":"Loke Uei","LastName":"Tan"},
- <m:properties>

<Driver>
<d:FirstName>Derek</d:FirstName>
<d:LastName>Snyder</d:LastName>
</m:properties>
</content>

</entry>

JSON
- <entry>

{"DistributionCenterId":1,"DriverId":3,"FirstName":"Dan","LastName":"Bouie"},

- <author>
<name />
</author>

<FirstName>John</FirstName>

REST-XML

OData
- <m:properties>

{"DistributionCenterId":1,"DriverId":4,"FirstName":"John","LastName":"Dietz"},

<LastName>Dietz</LastName>
<d:FirstName>Steve</d:FirstName>
<d:LastName>Hegenderfer</d:LastNam e>
</m:properties>

639
</content>

WebRequest, etc.)
</Driver>
</entry>
- <entry>

<Driver>
{"DistributionCenterId":2,"DriverId":5,"FirstName":"Derek","LastName":"Snyder"},
- <author>
<name />

1.2kb
</author>

8.5kb <DistributionCenterId>2</DistributionCenterId>
- <m:properties>


{"DistributionCenterId":2,"DriverId":6,"FirstName":"Steve","LastName":“Harris"},
<d:FirstName>Chip</d:FirstName>

bytes
<d:LastName>Vollers</d:LastName>
</m:properties>
</content>

<FirstName>Derek</FirstName>
</entry>
- <entry>

<LastName>Snyder</LastName>
- <author>
<name />

{"DistributionCenterId":2,"DriverId":7,"FirstName":"Chip","LastName":"Vollers"},
</author>

</Driver>

– Wire format choices (SOAP, JSON, POX,
- <m:properties>

<Driver>
<d:FirstName>James</d:FirstName>
<d:LastName>Pratt</d:LastName>

{"DistributionCenterId":2,"DriverId":8,"FirstName":"James","LastName":"Pratt"}]
</m:properties>
</content>

</entry>
</feed>
The same list of 8 Customers using SOAP and a DataSet dropped us down to 3 kb but still too big for my taste.
<?xml version="1.0" encoding="utf-8"?>
<DataSet xmlns="http://tempuri.org/" >

<xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/20 01/XMLSchema " xmlns:msdata="urn:schemas-micr osoft-com:xml -msdat a">
<xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="Driver">

<FirstName>Steve</FirstName>
<xs:complexType>
<xs:sequence>
<xs:element name="DriverId" type="xs:int" minOccurs="0" />
<xs:element name="DistributionCenterId" type="xs:int" minOccurs="0" />
<xs:element name="FirstName" type="xs:string" minOccurs="0" />

<LastName>Hegenderfer</LastName>
<xs:element name="LastName" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>

</Driver>
</xs:complexType>
</xs:element>
</xs:schema>
<diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com :xml-m sdata" xmlns:diffgr="urn:schemas-microsof t-com:xml-diff gram-v 1">
<NewDataSet xmlns="">

<Driver>
<Driver diffgr:id="Driver1" msdata:rowOrder="0">

etc.)
<FirstName>Rob</FirstName>
<LastName>Tiffany</LastName>

</Driver>
<FirstName>Loke Uei</FirstName>

<LastName>Tan</LastName>
</Driver>

<FirstName>Chip</FirstName>
<FirstName>Dan</FirstName>
<LastName>Bouie</LastName>
</Driver>

<LastName>Vollers</LastName>
<FirstName>John</FirstName>
<LastName>Dietz</LastName>
</Driver>

</Driver>
<FirstName>Derek</FirstName>
<LastName>Snyder</LastName>
</Driver>

<Driver>
<FirstName>Steve</FirstName>
<LastName>Hegenderfer</LastName>

</Driver>
<FirstName>Chip</FirstName>

<LastName>Vollers</LastName>
</Driver>

<FirstName>James</FirstName>
<FirstName>James</FirstName>
<LastName>Pratt</LastName>
</Driver>
</NewDataSet>
</diffgr:diffgram>

<LastName>Pratt</LastName>
</DataSet>

</Driver>
</ArrayOfDriver>

Communications: Cloud-initiated
• Push Notifications
– Single connecting between the device and the
notification service
– Bandwidth- and battery-friendly
– No guarantee of delivery

Communications: Subscribing to Push
• Device requests a
channel
• *NS returns channel Web *NS
• Device sends URL to Role
cloud
– Channel URL is stored
in cloud
• Cloud sends notification
• *NS pushes to device

Communications: Cloud-initiated to
device?
• Common pattern
– Use cloud-initiated push to
tell the device to call to a
service Web *NS
Role
• Cloud sends notification
• Notification services
pushes to device
• Device receives message
and calls to a service
• Web Role sends a
response

Notifications: Different services
• Windows 8: Windows Push Notification
Service (WNS)
• Windows Phone: Microsoft Push Notification
Service (MPNS)
• iOS: Apple Push Notification Service (APNS)
• Android: Cloud To Device Messaging (C2DM)
• …

Platform Services
• Caching
• Traffic Manager
• Content Delivery Network (CDN)
• SQL Azure Data Sync

Windows Azure Toolkits for Devices
• Easier for device developers to use
Windows Azure
– Windows Phone:
http://bit.ly/watwp7
– iOS: http://bit.ly/watios
– Android: http://bit.ly/watandroid
• Toolkits include:
– Native libraries (e.g. .NET,
Objective-C)
– Samples
– Project templates
– Documentation

Windows Azure Toolkit for Windows 8
• Deliver a Push Notification Cloud Service with ease.
• VS 2010 Project Template for Windows Azure
• Dev 11 Project for Client
• Samples:
– ACS Metro Style App
– Margie’s Travel
– Push Notification Worker
• Documentation
• Download at: http://watwindows8.codeplex.com/

demo
Show how the toolkits work

Windows Azure Office Hours
• Talk to an expert
• Download the SDK and toolkits
• Get a free trial
• Enter to WIN a
Samsung Focus Windows phone

Vote your evaluation

This session was . . .
• A little lite
• Just right
• More than I hoped for!

Nick harris-sic-2011

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (8)

Similar to Nick harris-sic-2011

Similar to Nick harris-sic-2011 (20)

More from Seattle Interactive Conference

More from Seattle Interactive Conference (20)

Recently uploaded

Recently uploaded (20)

Nick harris-sic-2011