This document discusses Microsoft Azure Mobile Services, which provide a comprehensive set of services to enable developers to quickly build, deploy, and manage cross-platform mobile applications. Azure Mobile Services allow storing data in SQL databases or NoSQL stores, provide backend services for authentication, push notifications, and more. The services can be accessed from any mobile or web application using client SDKs or a REST API.
4. Microsoft
Comprehensive set of services
that enable you to quickly
build, deploy and manage
applications across a global
network of Microsoft-managed
datacenters
10. Fortune 500 using Azure
>57% >300k
Active websites
More than
1,000,000
SQL Databases in Azure
>30TRILLION
storage objects >300MILLION
AAD users
>13 BILLION
authentication/wk
>3
MILLION
requests/sec
>1.65MILLION
Developers registered
with Visual Studio Online
11. Azure is open across the stack
Ecosystem Supported
Languages
CMS
Devices
Databases
Operating
systems
Microsoft 1st Party Support
12. Windows Azure Storage
Scalable, durable, and available
Anywhere at anytime access
Only pay for what the service uses
Use from Windows Azure Compute
Use from anywhere on the internet
13. Azure
TABLE
Storage:
• Storage Account: All access to Azure Storage is done through a storage account.
• Table: A table is a collection of entities. Tables don't enforce a schema on entities, which means a single table can contain
entities that have different sets of properties. The number of tables that a storage account can contain is limited only by
the storage account capacity limit.
• Entity: An entity is a set of properties, similar to a database row. An entity can be up to 1MB in size.
• Properties: A property is a name-value pair. Each entity can include up to 252 properties to store data. Each entity also
has 3 system properties that specify a partition key, a row key, and a timestamp. Entities with the same partition key can
be queried more quickly, and inserted/updated in atomic operations. An entity's row key is its unique identifier within a
partition.
16. Node.js
Express
.NET
Web API
SQL Table
Storage
Blob
Storage
WNS &
MPNS
APNS GCM
Mongo
DB
Notification
Hubs
Source
Control
Facebook Twitter Microsoft Google Azure Active
Directory
Windows Store
iOS
Android
Xamarin
Phonegap
Windows Phone
iOS
Android
HTML 5/JS
SDKs
RESTAPI
Hybrid
Connections
23. Windows Azure Web Sites
powerful web sites in seconds
start simple
start free, scale up and out as
you go, friction-free and
without the headaches
code smart
with classic asp, asp.net, php or
node.js, develop on Windows,
OSX or Linux
go live
deploy live in seconds, easily
monitor performance, rapidly
diagnose and fix issues
35. Resources:
35
Mobile Services
http://azure.microsoft.com/en-us/services/mobile-services/
Mobile Services Documentation | Azure
http://azure.microsoft.com/en-us/documentation/services/mobile-services/
Azure Mobile Services Team Blog - Site Home - MSDN Blogs
http://blogs.msdn.com/b/azuremobile/
Get started with Mobile Services
http://azure.microsoft.com/en-us/documentation/articles/mobile-services-windows-phone-
get-started/
Azure Readiness / DevCamp
https://github.com/Azure-Readiness/DevCamp
Editor's Notes
Slide Objectives:
Detail the differing compute options and scenarios where each would be used
Slide Objectives:
Define the Windows Azure storage and the great benefits this service provides
Speaking Points:
The Windows Azure storage services provide storage for binary and text data, messages, and structured data in Windows Azure
Scalable
Durable
Available
Cost
REST
Geo-redundant storage provides the highest level of storage durability by seamlessly replicating your data to a secondary location within the same region
Locally redundant storage provides highly durable and available storage within a single location.
Microsoft monitors the service, provides patches, handles scaling, and does the other work needed to keep the service available.
Notes:
Slide Objectives:
Provide broad overview of WA Mobile Services features
Speaking Points:
WAMS
No hassles, no deployments, no fear
Windows 8 client SDK
Support for iPhone, Windows Phone and Android coming soon
Data
Structured Storage with SQL Database
Automatic service api generated for storage
Rich querying capability
Notifications
Integrates with WNS to provide Toast, Tile, Badge and Raw notifications
Clean object model to compose notifications
Server Logic
Automatic CRUD service api generated
Ability to author server logic that intercepts CRUD operation pipeline
Auth
Authenticate against Windows Live
Table level authorization with no code
More granular control with server side scripts
Scale out and Scale up
Slide Objectives:
Provide broad overview of WA Mobile Services features
Speaking Points:
WAMS
No hassles, no deployments, no fear
Windows 8 client SDK
Support for iPhone, Windows Phone and Android coming soon
Data
Structured Storage with SQL Database
Automatic service api generated for storage
Rich querying capability
Notifications
Integrates with WNS to provide Toast, Tile, Badge and Raw notifications
Clean object model to compose notifications
Server Logic
Automatic CRUD service api generated
Ability to author server logic that intercepts CRUD operation pipeline
Auth
Authenticate against Windows Live
Table level authorization with no code
More granular control with server side scripts
Scale out and Scale up
Slide Objectives:
Outline the Key Scenarios Mobile Services can be used for
Things to note
Connection string/application key
Data (nothing there to start)
authentication
Slide Objectives:
Jump to VS and Demo the New Mobile Service Create a new Windows 8 application experience in the portal
Create a table
Generate ToDoItem table (simplifies the demo)
Show the cloud icon
Things to show
Records (will come to that soon)
Scripts
authentication
- go to configure, enable editing online in Visual studio online
Copy and paste code in
Save and have the user
In minutes, have audience go to public website and push data to Azure Table
Slide Objectives:
Detail the Server Logic capability
Speaking Points:
On creating of a Mobile Service a dynamic REST API is generated that sits on top of your structured storage
Dynamic Schema
When Dynamic Schema is enabled, your Mobile Service will automatically add columns to tables as necessary to store incoming data.When Dynamic Schema is disabled, your Mobile Service will only accept data whose properties correspond to existing columns on your tables.
Slide Objectives:
Explain how Windows Azure websites are simple, easy, and open.
Notes:
Git Deployment is Native, or through a Service hook from CodePlex, GitHub or BitBucket
Export sample app (mention different export options Windows, IOS, Android with Natvive SDKS)
Show native SDK for Windows Universal apps
Initializing AzureMobileService object with Connection string/url and App Key in App.Xaml
Run sample app to show pushing and pulling of data to and from Azure
Show results appearing in table, just like we did from the website
Slide Objectives:
Builds on the getting started application to Demonstrate how to add some simple server logic to an operation like the Insert operation. See example in video here http://go.microsoft.com/fwlink/?LinkID=267130&clcid=0x409
Slide Objectives:
Detail Auth options
Speaking Points:
Support for additional auth providers such as Facebook are coming soon
Windows Azure Mobile Services enables you to set the following permissions on table operations:
Everyone: This means that any request for the operation against the table is accepted. This option leaves your data wide-open for everyone to access. Anybody with the Application Key: Only the correct application key is required to perform the operation. The application key is distributed with the application. Because this key is not securely distributed, it cannot be considered a security token. To secure access to you mobile service data, you must implement authentication. Only Authenticated Users: Only authenticated users are permitted to perform the operation. In this preview release, clients are authenticated by Live Connect services. Scripts can be used to further restrict access to tables based on an authenticated user. Only Scripts and Admins: The operation requires the service master key, which limits the operation only to registered scripts or to administrator accounts.
The user parameter is available in all server side scripts methods and can be used to add more granular auth polices on you CRUD operations
Notes:
Slide Objectives:
Detail Auth options
Speaking Points:
Support for additional auth providers such as Facebook are coming soon
Windows Azure Mobile Services enables you to set the following permissions on table operations:
Everyone: This means that any request for the operation against the table is accepted. This option leaves your data wide-open for everyone to access. Anybody with the Application Key: Only the correct application key is required to perform the operation. The application key is distributed with the application. Because this key is not securely distributed, it cannot be considered a security token. To secure access to you mobile service data, you must implement authentication. Only Authenticated Users: Only authenticated users are permitted to perform the operation. In this preview release, clients are authenticated by Live Connect services. Scripts can be used to further restrict access to tables based on an authenticated user. Only Scripts and Admins: The operation requires the service master key, which limits the operation only to registered scripts or to administrator accounts.
The user parameter is available in all server side scripts methods and can be used to add more granular auth polices on you CRUD operations
Notes:
Slide Objectives:
Continue building out the Getting Started sample by adding Push Notifications to send a toast or tile
Notes:
Full demo script and snippets available in the links on slide 2.
Slide Objectives:
Detail the push notification lifecycle to give context for the demo coming up
WNS is free
Speaking Points:
Show the start screen and talk about how push notifications can be used to lightup the start screen
Green components are those FREE services Microsoft provides
Blue components are those components that the application developer must write.
Step 1 – using the WinRT API request a channel. A channel uniquely identifies an app and its tile.
Step 2 – channel is then registered and stored in your Mobile service
Step 3 – When your application specific logic determines that it is time to send a notification you can retrieve the channel and compose a notification to be sent. This is a two step process that first requires your service to auth against WNS and then compose and send a notification. Mobile Services makes this step incredibly easy.
Step 3 - part 2 – WNS will take care of delivering the notification and the Notification client platform will deal with surfacing that notification for you and rendering the tile/toast/badge etc
Slide Objectives:
Detail the types of notifications available with WNS
Detail how WNS Auth credentails are captured
Detail the API namespace for push
Speaking Points:
Talk through slide
Raw notification support coming soon.
Notes:
Any notes go here
Slide Objectives:
Provide broad overview of WA Mobile Services features
Speaking Points:
WAMS
No hassles, no deployments, no fear
Windows 8 client SDK
Support for iPhone, Windows Phone and Android coming soon
Data
Structured Storage with SQL Database
Automatic service api generated for storage
Rich querying capability
Notifications
Integrates with WNS to provide Toast, Tile, Badge and Raw notifications
Clean object model to compose notifications
Server Logic
Automatic CRUD service api generated
Ability to author server logic that intercepts CRUD operation pipeline
Auth
Authenticate against Windows Live
Table level authorization with no code
More granular control with server side scripts
Scale out and Scale up