Putting the Cloud in Your Pocket with Azure Mobile Services (.NET)
Download as PPTX, PDF0 likes783 views
The document discusses Microsoft Azure Mobile Services and provides an overview of its key capabilities including data storage, server-side logic, authentication and authorization, push notifications, and pricing and scaling options. It describes how mobile services provides a backend for building mobile apps that can access cloud services and resources through a REST API.
Putting the Cloud in Your Pocket with Azure Mobile Services (.NET)
- 1. Putting the Cloud in Your Pocket Using Azure Mobile Services (.NET) Consulting/Training
- 2. Thank You to Our Sponsors! Consulting/Training
- 3. Cloud and mobile are in fact one and the same. The mobile devices that users are flocking to are useless without the cloud. And the cloud…is just a theory until you have a device that's both powerful enough to run apps that can take advantage of it and mobile enough that those apps are with you all the time, and working on your behalf. Paul Thurrott Will IT Ever Buy into “Mobile First, Cloud First”? 4/29/2014 http://j.mp/1jjFzs2 Consulting/Training
- 4. Azure Mobile Services Microsoft Azure Consulting/Training Media Services Access Control Azure Active Directory Service Bus Content Delivery Network Azure SQL Database Azure Storage Virtual Machines Web Sites Cloud Services
- 5. "If you wish to make an apple pie from scratch, you must first invent the universe." - Carl Sagan Ease-of-use Control Consulting/Training
- 6. Introducing Mobile Services (.NET Backend) Data Storage Server-Side Logic Authentication & Authorization Push Notifications with Notification Hubs Prices & Tiers Consulting/Training Agenda
- 7. The Two Parts of Azure Mobile Services A factory for creating REST APIs that can access several back-end services: Provisioning and Management of Storage Server-Side Business Logic with Source Control Integration Authentication & Authorization Push Notification Integration Scheduled Script Execution Consulting/Training Client libraries Simplify using the REST APIs provided by the server Client-side tooling (WAB, Offline Data Sync with SQLite) Source code for the client libraries is available on GitHub: http://github.com/WindowsAzure/azure-mobile-services
- 8. Getting Started with the Windows Azure Mobile Services Portal Consulting/Training
- 9. Data Storage Out of the box support for SQL Azure, Azure Tables, Mongo DB For SQL Azure Consulting/Training Access via EF6 Code-First Automapper support is included to provide DB Entity to DTO Conversions Use DB Migrations for schema updates 3 Steps: Data Model, Data Context, Data Controller
- 10. Consuming Data Tables (.NET apps) With the .NET client library, apps can either use strongly typed data objects Consulting/Training or dynamic JSON objects With strongly-typed data, object/table and property/column names can be aliased Using the DataTable attribute or the JsonProperty attribute Table operations include Query(where, skip/take, orderby/thenby) Lookup (find by id) Insert Update Delete
- 11. Server-Side Business Logic 3 Execution Models for Server Code Table Controller Methods (CRUD) Consulting/Training Custom API REST Endpoints Scheduler Jobs Services property provides access to Log, Push, Settings, Properties Functionality can be extended with NuGet or other Assembly references
- 12. Consulting/Training Working with Data
- 13. Authentication & Authorization Consulting/Training Out of box support Microsoft Account, Twitter, Google, Facebook, Azure Active Directory “Secret Values” stored on the server in the Portal, behind the firewall Authentication Flows Server-Flow: Server (Mobile Services) manages the authentication process Client-Flow: Client authenticates on its own, passes token to server Authorization Scoped within the Controllers – entire controller or individual methods Levels: Anonymous, Application, User, Administrator Custom Authentication Extensibility
- 14. AuthN – Custom Scopes in the Server Flow Facebook, Google, Microsoft Account Specify in the portal’s “app settings” section The authentication token that is obtained during login then supports requests for additional information from the identity provider Consulting/Training Available Values Microsoft Account Scopes - http://j.mp/MicrosoftAccountScopes Facebook Login Permissions - http://j.mp/FacebookPermissions Google Authorization Scopes - http://j.mp/GoogleScopes
- 15. Using Authentication & Authorization Consulting/Training
- 16. Push Notifications Support for Windows (WNS), Windows Phone (MPNS), iOS (APNS), Consulting/Training Android (GCM) Notification Hub provisioned alongside your Mobile Service Register for Push either via the Client API or relayed through the server Optionally provide tags with registration Server sends platform-specific push messages to the Notification Hub along with optional tags to filter targets
- 17. Notification Hub Push Notification Lifecycle 2 4 Consulting/Training 1) The app requests and is issued a notification channel 2) The app registers this channel information and optionally some tags with the Mobile Service’s Notification Hub 3) An external event occurs that causes the Internet service to decide it should send notifications 4) The Internet service tells the Notification Hub to send notifications, optionally supplying one or more tags and optionally indicating a template to use 5) The Notification Hub iterates over its own list of applicable registrations, composes the payload appropriately, and sends the correct request to the notification services, managing failures, expired registrations, etc. 6) The notification services route notifications to the appropriate devices, where the payload and device settings determine how it should be displayed App App Service Device OS Notification Service 3 Notification Hub 1 6 5
- 19. Other Offline Sync in the Client SignalR Integration for Real-Time Consulting/Training Communication Resource Broker for Azure Storage Access Integration With Azure API Management (Apiphany) Integration with SQL Azure Auditing Other Topics Data Support for Hybrid Connections Azure Tables, MongoDB AuthN Client-Flow Authentication Custom Scopes Custom Authentication Provider Notifications Notification Hub Templates
- 20. Pricing and Scaling Options Dev/Test Production Deployment Free Instance Basic Instance Standard Instance Price Free (up to 10 services/month) $14.99/unit/month $139.99/unit/month API Calls 500K/mo (prorated daily) 1.5M/unit/month (pr. daily) 15M/unit/month (pr. daily) Active Devices 500 devices/day Unlimited Scale 1 unit (no AutoScale) Up to 6 units Unlimited units Notifications Free Tier included (up to 1M) Basic Tier Incl (up to 10M) Standard Tier Incl (up to 10M) Scheduled Jobs 1 scheduled job Consulting/Training 1 execution/hour Up to 10 scheduled jobs 50K job executions Up to 10 scheduled jobs 500K job executions Other 60 CPU minutes/day 165 MB outbound data/day SQL Database 1 20 MB database (free for 12 months) can be created per subscription, pay for other DB tiers
- 21. Pricing and Scaling Options – Notification Hubs Free Instance Basic Instance Standard Instance Consulting/Training Price Free for 1 million pushes $10 base charge / month for 10 million pushes + $1 for 10M-100M + $1 for 100M+ $200 base charge / month for 10 million pushes + $10 for 10M-100M +2.50 for 100M+ Broadcast size Up to 3,000 tags, up to 10,000 devices per tag Unlimited devices & tags Active Devices Unlimited Other Queryable Audience Scheduled Push Telemetry Bulk Import Multi-Tenancy
- 22. Code Samples: Windows: http://j.mp/MobileServicesWindowsStoreSamples Windows Phone: http://j.mp/MobileServicesWindowsPhoneSamples iOS: http://j.mp/MobileServicesIOSSamples Android: http://j.mp/MobileServicesAndroidSamples Consulting/Training Resources Videos: Channel 9 mini-videos: http://j.mp/MobileServicesChannel9Series (38) Build 2014: http://j.mp/MobileServicesBuild2014 (3) TechEd NA: http://j.mp/MobileServicesTENA2014 (3) Documentation: Tutorials / Resources: http://azure.microsoft.com/en-us/develop/mobile/ Team Blog(s): http://blogs.msdn.com/b/azuremobile/ (prior to 7/8/2014) http://azure.microsoft.com/blog/
Editor's Notes
- #4: The Mobile Services story – Using Azure, but emphasis is on keeping your focus on creating your apps
- #6: The Mobile Services story – Using Azure, but emphasis is on keeping your focus on creating your apps
- #9: Marketing Message: A Windows Azure service offering that simplifies the creation of backend services for mobile apps. Mention that the REST uses a subset of OData - the Open Data Protocol developed by Microsoft Emphasize the Client libraries and the platforms they currently target
- #16: This doesn’t “automagically” return more than just the token & simple ID’s – it just means that requests to the IdP are now allowed to ask for more information. This implies that an additional request is still required! (Which is largely the norm) http://azure.microsoft.com/blog/2014/10/02/custom-login-scopes-single-sign-on-new-asp-net-web-api-updates-to-the-azure-mobile-services-net-backend/ http://blogs.msdn.com/b/carlosfigueira/archive/2013/12/12/expanded-login-scopes-in-azure-mobile-services.aspx
- #19: More advanced notification hub subscriptions, options (authentication levels, custom actions with notificaitons, templates, etc) - http://blogs.msdn.com/b/azuremobile/archive/2014/04/08/push-notifications-using-notification-hub-and-net-backend.aspx
- #22: An active device = device making a request OR being sent a push notification (client libraries provide device Id through HTTP header) One 20MB Azure SQL Database is available per subscription for the first twelve months of use; standard rates apply thereafter. Data txfer costs are included Autoscaling: Basic, Standard only. Periodically (period?) checks daily number of API calls to and from and scales up by a unit if within 90% of API quota (until max) At start of each day, scales down to set minimum. Guidance is to set minimum to meet daily traffic + small spikes…set max to handle bursts.