Azure Mobile Services : Service Enablement at its best
•Download as PPTX, PDF•
0 likes•474 views
This document provides an overview of building mobile services with Microsoft Azure Mobile Services using Visual Studio. It discusses key features like supporting various backend databases, client SDKs, push notifications, authentication including Azure Active Directory, offline sync, and tools for monitoring and scaling. The document also includes demos of storing and querying data, authentication, integrating blob storage, and using offline sync.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Azure Mobile Services : Service Enablement at its best
Similar to Azure Mobile Services : Service Enablement at its best (20)
Recently uploaded
Recently uploaded (20)
Azure Mobile Services : Service Enablement at its best
- 1. Learn. Connect. Explore.Learn. Connect. Explore.
- 2. Building Microsoft Azure Mobile Services with Visual Studio Poonam Sampat Technical Evangelist @sampatpoonam Ruhani Arora Technical Evangelist @infinitydlimit
- 3. I am familiar with Mobile Services
- 5. Overview
- 6. 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 Sencha Windows Phone iOS Android HTML 5/JS SDKs RESTAPI Hybrid Connections
- 8. Based on Web API Supports various data stores: • Azure databases • Table Storage • MongoDB • Client NuGet • Runtime available on NuGet Visual Studio support: • Scaffolding • IntelliSense • Local F5 • In-browser test client • Remote debugging • Publish via Web Deploy • Source control using TFS • View runtime logs • Send test messages • View registrations • Facebook • Twitter • Google • Microsoft Account • AAD Uses Notification Hubs integration for high-scale, cross- platform push
- 10. Demo Storing and accessing data with SQL
- 11. Authentication
- 12. Extend line-of-business to mobile Bring turn-key login experience with corporate credentials to mobile developers Enable applications built around organizational structures
- 13. Facilitates login to AAD-protected resources Provides single sign-on to multiple enterprise resources Available for Windows Store, iOS, and Android
- 15. Demo with AAD and Mobile Services
- 16. Blob Storage + Mobile Services
- 17. Cost effective, scalable, and accessible from anywhere Imagine malicious users uploading random files to your storage account Allows clients to read/write/update data without a storage account key Obtain a restricted token that allows you to access storage account for a short period of time
- 19. CloudBlobClient blobClient = new CloudBlobClient(blobEndpoint, new StorageCredentials(storageAccountName, storageAccountKey)); CloudBlobContainer container = blobClient.GetContainerReference(item.containerName); await container.CreateIfNotExistsAsync(); SharedAccessBlobPolicy sasPolicy = new SharedAccessBlobPolicy() { SharedAccessStartTime = DateTime.UtcNow, SharedAccessExpiryTime = DateTime.UtcNow.AddMinutes(5), Permissions = SharedAccessBlobPermissions.Write }; String sasContainerToken = container.GetSharedAccessSignature(sasPolicy); String SASUri = sasContainerToken ;
- 20. Offline Sync
- 21. Uses SQLite Backing Store, runs cross platform.
- 22. var table=App.MobileService.GetSyncTable<Feedback>(); if (!App.MobileService.SyncContext.IsInitialized) { var store = new MobileServiceSQLiteStore("localsync12.db"); store.DefineTable<Feedback>(); await App.MobileService.SyncContext.InitializeAsync(store, new MobileServiceSyncHandler()); }
- 23. await table.PullAsync(); var list = await table.OrderBy(a=>a.Id).ToListAsyn(); table.Insert(new TodoItem(..)); service.SyncContext.PushAsync();
- 25. store data in the cloud authenticate your users interact with Azure storage and other third party resources offline sync diagnostics and scale
- 26. Related sessions Notification Hubs Use Xamrain to develop cross platform applications
- 28. Your Feedback is Important OPTION 3: Feedback stations outside the hall Fill out evaluation of this session and help shape future events. OPTION 1 OPTION 2 Replace this space with the actual QR Code
Editor's Notes
- Have you downloaded the feedback application? If not I request you to go ahead and download the same. For folks who have not downloaded what all do you think a feedback application should be able to do? Allow you to rate and store feedback for all the session that you are have attended, also if you rate is bad we have a slap noise generated. I am kidding.!! See all the sessions that are lined up for today and tomorrow. Favorite your sessions. Should be able to show a toast if a session is changed or moved, or delayed for some reason. Say you want add a little authentication, to allow access to only folks within some group. And you want all these requirements supported on various platforms…maybe an Iphone, android phone or windows phone. Wow you have a rich set of requirements for this application, you want to store data, authenticate, provide offline support, send push notifications, sounds like lots of work, with lot of backend technologies you need to speak to, different frameworks involved and different tools. Well that is a big no. My name is Poonam Sampat , a technical evangelist , who evangelizes Azure along with Ruhani Arora who is my colleague today we here to tell you that using Microsoft Azure mobile Services and the IDE that we all use and love VS that you can spin up a back end that spans all your needs, that can give your application a backend that meets all your requirements. Rich set of requirements -> store data, authenticate users, send push notifications and all of this has to be cross platform. Sounds like lots of works, lot of backend technologies, frameworks, different tools. Well the answer is “No”. Over the weekend there was an article in deccan herald which spoke about how there is a phrase “appoholics” And it also spoke about how global mobile app revenues mounted to around $18.56 billion dollars and how by 2017 it will grow to a whopping $76.52 billion. So the point I am driving is that having that one app idea, leveraging something like an azure mobile service how each one of you can create your own brands.
- By a show of hands how many of you are familiar with Mobile Services. For how many of you this a true statement.
- We will do a good overview of mobile services , key principles of Azure Mobile Services and how that will make sense for any data driven application that you are building. Then we will go hands deep into Visual Studio, take a windows app and create a backend and show you how easy it is.
- What is Azure Mobile Services? So mobile apps have data, you have to store your data somewhere, cloud is an obvious option for storing data, so mobile services has an option to store data and do smart querying on the data.You can do smart queries, which are built on Odata, Odata is very well integrated on Web API, client sends an oData query the server executes query, brings the results back to client. Support for CRUD operations. The database that we support out of the box are - we support SQL Db out of the box, you can use table storage ,blob storage, mongo db, we announced hybrid connections, you can bring your own database. We give a free tier , with SQL DB which you can start trying. We allow to authenticate your users against different providers, standard ones, facebook, twitter, Microsoft account, google and azure active directory. You have to register with these providers and tell azure mobile services about your registration, users will be able login via those accounts to your application. So you don’t have to store username and passwords, but if you want to you can store the details and we support azure active directory for the same. One more possibility is to have custom authentication supported, well that is not mentioned, that’s the speed at which we are delivering. Again authentication is a important concern and it is handled by the backend. Also apart from authentication, you can do levels of authorization. Other thing mobile app need is Push notifications, and notification hubs,send push notifications which gives you classes which you can use to high volume, low latency push notifications messages you can reach out to iphones, ipads,google tablets, android phones, android devices, windows phones & kindle fire. We are not going to go deep dive on the notification hubs, if you want to know more, please attend my collegues Abhishek’s session at 6:00pm in the same hall. The way you interface with these different technologies is you can use REST API, and if you don’t want to muck with these rest api, we have client library for all major platforms. Here I am at a Microsoft premium conference with a Microsoft logo and talking to you about how we support so many platforms and devices, this is the openness that Microsoft has embraced. Another feature is we support Custom API, API Controllers which expose arbitrary http endpoints. If you want to do operations not related to the Database you can use custom API. All this is hosted on Azure. Offline Sync: Major feature which we will be demo today. Users can work offline, and there is support for pushing and pulling changes from the services and there is also support for conflict management. Like merge the results ignore records. Two kinds of runtimes node.js and .net. Out .net runtime powered by web api.
- After we released the node js backend, we went back to community and the customers, they said why don’t we expose something with .net so that it is easy to build a backend, time to learn node.js would disappear.
- .Mobile Services what is it? In a nutshell it is web api but customized for mobile scenarios. We support Data, Auth and Push. What sets the .net mobile services apart is the VS rich tooling. You have nuget packages that you use for you windows store/phone apps. If you are IOS or android again we have rich library that you can use for consuming these .net mobile services. Great scaffolding, we wanted to minimize the code you need to write. We give you intellisense. We give you f5.We have a test harness which allows you to view the api but also try them. We also give you remote debugging, how many are familiar with remote debugging? At a high level, you are setting a break point on your mobile service which is in the cloud and debugging it as if it is on your machine. You can publish your mobile service ,so unlike JavaScript you are debugging live and writing against live services, in VS you can do the development and deploy once you are ready. Standard source control story, you can use TFS or preferred source control. View runtime logs from within VS. What I mean here is typically once the mobile services is up and running I want to check all the events, like success and failures , if something failed why did it fail? Get my run time logs within VS. Send test messages for notification hub & view registrations.
- [Ruhani] Demo1: Storing and accessing data with SQL. Show the application, without connecting to any backend. Open new VS instance and create mobile services backend, create a new project select Cloud->Windows Azure Mobile Services template. Talking points: Mobile services project template is a customized web api template,taken out things like views and added packages , we have preloaded with Dataobject and a controller to give a sense of CRUD APIs. Open solution explorer -> navigate to Dataobject, show it inherits from entity data. TodoItemController-> show the CRUD APIs. Pause, [Poonam]I will take over and talk a little here about schedule jobs. If you want you can write your own data object class, which does not inherit from entity data. Schedule jobs are interesting, in your application you need to send periodic notification you can do that with mobile services, you need to deploy this and set a frequency.
- No we have an application that can store data on the cloud, now I would like to give access to only those folks who I think should have access to the application and data.
- We can do that via Azure Active directory. You must be wondering why active directory? We wanted to bring the Line of business mindset to mobile, give a turnkey login experience. Use corporate credentials instead of going thru google/twitter to login to the mobile application, so now you can build applications around organizational infrastructure. You have a large web service you have dev on call, to monitor if the webserver is down, you want a backend to notify his lead, his manager, the director, then ceo , without AD it is very difficult to define an escalation process. So how can we marry mobile services and active directory? We have something called as ADAL. It is a library Authentication Library.
- What is ADAL? Active Directory Authentication Library is used to authenticate all sorts of AAD resources, Login once and you can access mobile service, sharepoint sites. Also available for iOs and android.
- Your device connects to AD, and says hey I want a token to access the azure mobile service. It provides two things. Client Id and the name of the service it needs to talk to. Then AD says ok I can give you the token because of your identity and I know you are trying to access only this resource, the resource is given you permission to access it. Then after getting the token the client makes a request to the mobile service. So we need to register the service as well as the client application in as resources in AD. Lets see how we can implement the same in code.
- So that was a great demo, well the most important thing you need to keep in mind to get it going is register with Azure mobile services and AD. And one method you need to remember here is LoginAsync which will open up the entire oAuth flow.
- Now that I know that I can save the data on the cloud and only authorized users can access the data, I want to store files on the cloud.
- In a mobile application scenario say in the feedback application I would like to upload the feedback in the form of documents, in this scenario storage makes sense. To store documents, media files, videos, audio clipping blob storage is the storage option that Azure provides. As the name suggests you can store large binary objects. It makes perfect sense in this scenario since it is highly cost effective, and can be accessed from anywhere, by any client SDK. The way you access blob storage is you create a storage account, create a logical container and then a blob within that. To access the blob storage you need to know the storage access key. Now obliviously you cannot hard code you account key information in the client. Let me introduce to you shared access signatures, allow you to get a temp token with limited amount of time with limited access on the file. Mobile Services you would need to store files , most cost effective is using blob storage, scalable and it is accessible from anywhere.
- Device requests for SAS token for storage-> Mobile services has permission to talk to your storage account, it has the storage account key. The storage generates a SAS token, returns it to the device.
- Add this code at the services layer and generate the sas token. At the client based on the sas token they can request for the uploaded documents.
- Speaking points Very cool feature, and very easy to integrate with our app without making changes to the server, the whole backend will stay as is and we will make changes to the client , so users can work offline when the internet connection is not available. It uses SQl Lite as the default backing store, what ever you store offline, stuff that you cache when you are not connected to the internet is stored in SQL Lite database, which is a single file and there is a sql lite nuget package that you can download. What ever is stored offline is stored in SQLite. There is a nugget package for supporting SQLite. Push & Pull operations are manual, there is no magic synchronization there are functions that need to be called to pull data from the server or push data back to the server. So you work offline accumulate data and push them on the server. There is good conflict detection that is provided.
- You need to add a property called Version in the datamodel, the column is already present , client can see the version column. Defined table in the store Initialized the sync context Important to notice here is the MobileServiceSQLiteStore which abstracts the SQLlite database which implements an Interface, so if you don’t want to use SQLite, or just want to save on a file. Then give details on the table that you want to sync. Pending operations in the sync context queue: 0 Table: TodoItem Inserted into local store: 9e61196d-55df-4869-8b30-4a4a6eb792f2 Pending operations in the sync context queue: 1 Inserted another item into the local store: c349b30d-d603-48db-8509-b2fd170f4499 Pending operations in the sync context queue: 2
- Pull, here you provide a table and get data from the table and put it offline store. Call Push or Pull. Trigger synchronization. PushAsync() -> push data from local to the server.. Important thing to remember here is this sync is at the synccontext level. Pull Operation() Pulling data from the remote store, here it is advisable to get small set of items. Ideally a odata query shd be used. One thing to note when pull is performed if there are items in the pending synchronization queue, those items are first pushed over to the server. Synchandler, which determines what to do when a conflict occurs, you get both the local data and the server data, then you can determine based on the version which is higher and actually perform a merge or discard changes.
- Please ensure the below communicated We value your feedback Use any of the 3 options to provide feedback Option 1 -> QR Code Option 2 -> Feedback right through the app for the session Option 3 -> Via feedback stations You’ll also be entered into a daily prize drawing!