Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

26
Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization

Transcript of Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Page 1: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Building Windows Store Apps with Windows Azure Mobile ServicesNameTitleOrganization

Page 2: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Windows Azure Mobile ServicesDataPush NotificationsAuthSchedulerDiagnostics & Scale

Agenda

Page 3: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

What is Windows Azure Mobile Services?

Data

Notifications

Auth

Server LogicLogging & Diag

ScaleScheduler

Page 4: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Key ScenariosWindows Azure Mobile Services are ideal for:

Modern mobile appsWindows Store Apps, Windows Phone, iOS, Android

Common ScenariosReduces the friction associated with repeating common tasks such as user authentication, push notifications and structured storage

Rapid DevelopmentTime is money. Get your app up and running sooner when you use Mobile Services to configure a straightforward and secure backend in less than five minutes.

Page 5: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Getting Starteda backend for your mobile app in

minutes Demo

Page 6: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Structured StorageStructured Storage with SQL DatabaseIf using single database apps are partitioned by schema

AppX.TodoitemAppY.Todoitem

Manage data inPortal, SQL PortalSQL Management StudioREST APICLI Tools

Page 7: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Server Scripts

Automatic service REST API generated for storageDynamic Schema on/offAbility to author server logic that intercepts CRUD operation pipelineRich querying capability

Page 8: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Server LogicSupported Modules + Globals

mssqlrequestconsolepush.*tablesxml2jsstatusCodesWindows Azure Node SDKWindows Store Partners (Sengrid, Twillio, Pusher)

mssql.query(‘exec sprocDoStuff()', { success: function(results) {

console.log(results); }

});

Page 9: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

REST API to SQL type mappings

JSON Value T-SQL Type

Numeric values (integer, decimal, floating point)

Float

Boolean Bit

DateTime DateTimeOffset(3)

String Nvarchar(max)

Page 10: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Server Scriptsadding server scripts on CRUD

operations Demo

Page 11: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Push Notification Lifecycle Overview 1. Request Channel URI

2. Register with your Cloud Service

3. Authenticate & Push Notification

Windows 8

(1)

(2)

(3)

(3)

Page 12: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Push Notifications

Integrates with WNS to provide Toast, Tile, Badge and Raw notificationsPortal captures your WNS client secret and package SIDpush.wns.* provides:

clean easy object model to compose notifications

Performs auth against WNS for you

Page 13: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Push NotificationsDemo

Page 14: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Auth*Authenticate against Microsoft Account, Twitter, Facebook, GoogleTable level permissions for each CRUD operation

EveryoneAnyone with the Application KeyOnly Authenticated UsersOnly Scripts and Admins

More granular control with server side scriptsuser.level: {admin, authenticated, anonymous}

user.userId: id or undefined if not authenticated

Page 15: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Adding Authenticationhooking up Twitter in minutes Demo

Page 16: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

SchedulerExecute scripts on a Schedule

by Minutes

by Hours

by Days

By Months

Execute scripts on DemandExamples Periodic purge of old data

Poll and aggregate from 3rd party (Twitter, RSS, others)

Process/resize images

Schedule sending push notifications for a given time of day

Page 17: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

DemoPoll Twitter and send notification on a schedule Demo

Page 18: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Diagnostics, Logging and Scale

DiagnosticsAPI callsCPU TimeData Out

Loggingconsole.error(…)console.log(…)console.warn(…)

Scale - ComputeScale out instance countScale up VM size

Scale - StorageScale out mobile service tenant to dedicated SQL DBScale up SQL DB capacity

Page 19: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Diagnostics, Logging, Scale

Demo

Page 20: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Pricing during Preview

reserved modeservice level agreements

PreviewNo availability SLA*

General Availability99.9%

Shared Instance

Small instance is the only size available

Free - 10 applications with unlimited inbound data. Capped max of 165MB outbound data/day

Pay - SQL Database

Private VM

Small instance is the only size available

Free - unlimited inbound data. 165MB outbound data/day, excess charged.

Pay - SQL Database, Compute same reduced rate as Web Sites i.e 33% discount, excess outbound transfers starting at $0.12/GB

Up to 100 applications

shared mode

Page 21: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Pricing Example:

10 x Mobile Services on shared instances

100MB SQLDatabase

Unlimited ingress

<165MB daily egress

How?10 FREE mobile services on shared instanceIncludes 165MB/day of FREE egress from API calls Cost - All services sharing a 100MB DB is $5 USD / Month Use Pricing Calculator to Estimate your costs

=$5/ Month

Note: Free Egress is per subscription, not per mobile service

Page 22: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Don’t forget: Member OffersMSDN Subscribers up to $3700 / yearBizSpark members up to $3700 / yearMPN Members up to $1500 / yearWebsiteSpark up to $1500 / year

Full details here - http://www.windowsazure.com/en-us/pricing/member-offers/

Page 23: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Summary

Data

Notifications

Auth

Server LogicLogging & Diag

ScaleScheduler

Page 24: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Useful ResourcesGet a Windows Azure Free Trial Accounthttp://www.windowsazure.com/

Learn more & try tutorialsTutorials, Samples, Reference Docs: http://www.windowsazure.com/mobile

Help with Mobile ServicesQ&A Forum: Windows Azure Mobile Services ForumFeature Rqst: Windows Azure Mobile Services UserVoiceFeedback: [email protected]: @cloudnick (Windows 8, Windows Phone 8), @chrisrisner (iOS, Android)

Presentations, demos, hands on labsWindows Azure Training Kit: Download here

Page 25: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

Q&A• ….• ….• ….

Page 26: Building Windows Store Apps with Windows Azure Mobile Services Name Title Organization.

© 2011 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.