Cloud Powered Mobile Apps with Azure
Download as PPTX, PDF0 likes379 views
This document provides an overview of Microsoft Azure's Mobile Services platform for building cloud-powered mobile apps. It describes key Mobile Services components like structured storage, authentication, push notifications, and offline sync capabilities. It also covers the REST API, server-side scripts, .NET backend development, file storage, scheduling jobs, and scaling options. The document concludes with a recommendation to visit azure.microsoft.com to get started with a free Azure trial account and view additional learning resources.
Cloud Powered Mobile Apps with Azure
- 1. Cloud Powered Mobile Apps with Azure Toan Huynh Microsoft Azure
- 2. What is Mobile Services? 2 Storage Authentication Logic Push Scheduler
- 3. Structured Storage • Powered by SQL Database • Supports rich querying capabilities • Dynamic Schematization • Data management in: • Azure Portal • SQL Portal (Silverlight) • SQL Management Studio • REST API • Azure CLI Tools • SQL CLI 3Microsoft Azure
- 4. The REST API 4 Action HTTP Method URL Suffix Create POST /TodoItem Read GET /TodoItem?filter=id%3D42 Update PATCH /TodoItem/id Delete DELETE /TodoItem/id Microsoft Azure Base Endpoint: https://MobileService.azure- mobile.net/tables/*
- 5. Server Side Table Scripts 5 Node.js scripts Intercept CRUD requests to tables Passes through to SQL by default Fully customizable .NET Web API backend in Visual Studio MongoDB, Table Storage, SQL out of the box
- 6. .NET Backend • Web API based w/ additional functionality, developed in and deployed from Visual Studio • TableController data context can map to SQL, Table Storage, Mongo, etc • Pull in NuGet modules and other .NET libraries • Set permissions with attributes on classes • Local Debug 6Microsoft Azure
- 7. Custom API • Non-table based endpoints • Accessible from • GET • POST • PUT • PATCH • DELETE • For node.js logic in scripts like table endpoints • For .NET delivered through a WebAPI • Expose any functionality you want 7Microsoft Azure
- 8. File Storage • Don’t store files in Mobile Services DB • Use Mobile Service to provide a Valet Key Pattern to Blob Storage, aka BLOB SAS • Create table / custom API script to talk to Blob Storage • Script generates Shared Access Signature (SAS) URL • Script returns SAS URL to client app • Client app uploads data to blob storage directly • Store file URL in Mobile Service DB as needed • Blob storage costs less and is built for redundant file storage • Resource Broker extension for .NET and Node backends 8Microsoft Azure
- 9. Notification Hubs • Separate from Mobile Services • Can be used regardless of whether you’re storing data in Azure • Extremely scalable push notifications • Cross platform support • Push to iOS, Android, Kindle, Windows Phone, Windows Store • Tags (i.e. tie my registration to this topic or user ID) • Templates (i.e. when I get a push, send it in this format) • Server SDKs for .NET, Java, and Node (also open as REST API) 9Microsoft Azure
- 10. Data Authorization Per HTTP method auth options: • App Key Required • Not ideal for production use • Everyone • Authenticated Users • Admins and other scripts • Requires Master Key as header 401 Unauthorized response if security check fails 10Microsoft Azure
- 11. Offline support TableController (with optimistic concurrency) Mobile ServiceDevice SQL Database BYOD MongoDB Table Storage SQLite Explicit Push/Pull Conflict resolution
- 12. Offline Sync: Potential Uses • Improve app responsiveness by caching server data locally on the device • Make apps resilient against intermittent network connectivity • Allow end-users to create and modify data even when there is no network access, supporting scenarios with little or no connectivity • Sync data across multiple devices and detect conflicts when the same record is modified by two devices 12
- 13. Scheduled Jobs • Executes a script on defined schedule • Can be run on demand • Ideal for any backend data processing job • Length / frequency based of Mobile Service tier 13Microsoft Azure
- 14. Diagnostics, Logging, Scale 14 API Calls, # of Devices, Data Out Console Logging (auto error logging) Scale Service Based off API Calls Auto-scale to Save Money Free Tier for Mobile Free Tier for SQL
- 16. Demo: Mobile Services .NET Backend Creating a Leaderboard App
- 17. Resources • Get a FREE Microsoft Azure Trial Account: • http://azure.microsoft.com • Videos, Tutorials, and More • http://azure.microsoft.com/mobile • SDK Source Code on GitHub • https://github.com/Azure/azure-mobile-services • Contact Details • <Contact Info> 17Microsoft Azure
Editor's Notes
- #3: Speaking Notes Azure Mobile Services is a Backend-as-a-Service Instead of you having to design, build, test, deploy, manage, and upgrade your whole backend, we do it for you Features of Mobile Services Storage – SQL DB Authentication – built in support for social providers w/ ability to custom auth Backend logic – data validation, logical flows, etc Push Notifications – across all major mobile platforms Scheduler – backend job processing
- #4: Speaking points Mobile Service easily connects to SQL Database SQL offers rich querying and indexing capabilities Dynamic Schematization means you don’t have to be a DBA and manage schema Data can be managed in: Azure Portal (read and delete data) SQL Portal (Silverlight) SQL Management Studio (windows) REST API (used by SDKs) Azure CLI tools SQL CLI (Node module)
- #5: Speaking points This is the mapping for the REST API exposed by table storage Standard REST Anything that can talk REST can connect to your Mobile Service
- #6: Speaking points Node backend generates Node scripts for each table action Scripts intercept CRUD requests Pass to SQL by default Custom logic added here Edit in portal (NODE) .NET Backend creates Visual Studio project
- #7: Speaking points .NET backend is currently in preview Bases off of Web API Develop and deploy in VS (also create new Mobile Services with VS project template) Debug locally Can pull in NuGet and other .NET libs TableController is base for accessing data, can be overridden to talk to Table Storage, Mongo, etc Permissions handled as attributes on classes
- #8: Speaking points All scripts so far tied to a table action Custom APIs are non-table based endpoints Script functionality for normal HTTP methods
- #9: File storage SQL DB for Mobile Services not ideal for file data storage Best practice is to use Mobile Service as Proxy Mobile Service script generates SAS URL Client uploads file to SAS URL Valet Key Pattern http://msdn.microsoft.com/en-us/library/dn568102.aspx
- #10: Speaking points Notification Hubs are a separate service from Mobile Services but also used by Mobile Services Pushes to iOS, Android, Kindle, Windows Phone, Windows Store Extremely scalable (millions of pushes in minutes) Tags and templates Server SDKs: .NET, Java (beta), Node, REST API
- #11: Speaking points Data auth – locking data down Default is App Key Required, great for pre-release time period Not production ready due to key’s accessibility in public apps Authenticated users – requests must contain user ID and matching auth token Admins and other scripts – only external requests with Master Key make it through Otherwise 401 is returned
- #14: Speaking points Schedule jobs (scripts) can be run by the scheduler Ideal for any backend job processing (regular push notification, remove old data, etc) Length and how often you can run job based off tier of your mobile service
- #15: Speaking points Some default stats like # of api calls, # of devices connecting, amount of data out Api calls are important because that’s how mobile services’ scale is baed All console statements and errors go to logging area Auto-scaling helps save money Free tier for Mobile Services and SQL while developing
- #16: Speaking Notes Summarize earlier slide Azure Mobile Services is a Backend-as-a-Service Instead of you having to design, build, test, deploy, manage, and upgrade your whole backend, we do it for you Features of Mobile Services Storage – SQL DB Authentication – built in support for social providers w/ ability to custom auth Backend logic – data validation, logical flows, etc Push Notifications – across all major mobile platforms Scheduler – backend job processing
- #17: Demo: Getting Started Go to the portal Create a new mobile service (Node backend works with most of deck) Walk through Getting started screen Choose platform Download quick start Run quick start Save and update data Show data in portal (Node) Walk through client code that deals with Mobile Service
- #18: Speaking points Sign up for a free Azure trial Mobile Services are free to develop with (to a point) on non-trial subscription Additional videos, tutorials, samples available SDK source code (for Mobile Services and Notification Hubs) available in GitHub