Windows Azure Mobile Services, Connecting Cross Platform Devices


Published on

People are getting more and more connected and moving away from computers to using more mobile devices than ever before. Tablets, phones, slates are becoming the new computers.

All these devices and applications also need data, synchronization, security and much more. The broad reach, the number of devices and apps and the big amount of different platforms existing today, are pushing the needs for scalable and high available solutions running on a solid cloud platform, like Windows Azure.

One of the killer features of Windows Azure is WAMS, the Windows Azure Mobile Services. A Solid platform to connect cross platform devices and to open up a big set of features needed to build mobile applications.

In this session we will give you an introduction to WAMS, show you its true power and demonstrate how it can be used on multiple platforms to have one common way of connectivity. Managing and opening up your data to mobile users, while keeping the flexibility of validation and queries. Securing your applications by enabling authentication and authorization and by allowing the user to do single sign on or to use his favorite identity provider like Live, Facebook or Twitter. Enabling standard communication means like email and SMS, directly from your own application. And last but not least, enriching applications using push notifications, to send information from server to client and to notify users about new content.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Slide Objectives:Detail the structured storage featureSpeaking Points:Structured storage provided by WAMS is backed by a Windows Azure SQL DatabaseDB can be Multi-tenant i.e 10 Mobile services can all use the one SQL Database. In this scenario each DB is partitioned by SchemaMultiple ways admins can access the raw data being stored.
  • Slide Objectives:Detail the Server Logic capabilitySpeaking Points:On creating of a Mobile Service a dynamic REST API is generated that sits on top of your structured storageDynamic SchemaWhen 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:Detail the Modules and Globals available to server side scripts.Speaking Points:Talk through the slideA subset of Node.js modules are also supportedPerforming SQL queries is something that some people are not aware of. Instead of tables if you want to use mssql you can execute sql directly. One useful example of this would be to execute a store procedure
  • Slide Objectives:Detail the current REST API JSON value to T-SQL type mappingsSpeaking Points:Table shows the current JSON type mapping to T-SQL mapping used when columns are dynamically generated.As we iterate on mobile services you will see the list of type mappings grow
  • Slide Objectives:Detail Auth optionsSpeaking Points:Support for additional auth providers such as Facebook are coming soonWindows 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 operationsNotes:
  • Slide Objectives:Detail the push notification lifecycle to give context for the demo coming upWNS is freeSpeaking Points:Show the start screen and talk about how push notifications can be used to lightup the start screenGreen components are those FREE services Microsoft providesBlue 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 serviceStep 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 WNSDetail how WNS Authcredentails are captured Detail the API namespace for pushSpeaking Points:Talk through slideRaw notification support coming soon. Notes:Any notes go here
  • Slide Objectives:Detail what Mobile Services provides as far as Diagnostics, Logging and Scale is concernedSpeaking Points: Note when moving a Mobile Service from a multi-tenant DB to its own. Currently data is not automatically migrated.
  • Slide Objectives:Detail the free offer during Preview Speaking Points:10 FREE mobile services running on shared instances during Preview1 Mobile Service = 1 backend for an app. Each mobile service can utilize multiple features ie a mobile service for to do app can use user auth, multiple types of push, and structured storage and still count as one mobile service.WA free trial DB expires after 90 days. Important to note that BizSpark and MSDN subscriptions provide longer free DBNotes:SLAWhile Mobile Services is in preview, it can be used with apps in production, if customers ask for SLA and support, both can be provided by the product team upon request as part of the early adopters program, contact for details.
  • Notes:SLAWhile Mobile Services is in preview, it can be used with apps in production, if customers ask for SLA and support, both can be provided by the product team upon request as part of the early adopters program, contact for details.
  • Windows Azure Mobile Services, Connecting Cross Platform Devices

    1. 1. Windows Azure Mobile Services are ideal for:
    2. 2. Demo
    3. 3. Supported Modules + Globals mssql request mssql.query(select top 1 * from statusupdates, { success: function(results) { console console.log(results); push } } tables ); statusCodes
    4. 4. JSON Value T-SQL TypeNumeric values (integer, Floatdecimal, floating point)Boolean BitDateTime DateTimeOffset(3)String Nvarchar(max)
    5. 5. Demo
    6. 6. Demo
    7. 7. Demo
    8. 8. Diagnostics Scale - Compute Scale - StorageLogging
    9. 9. Demo
    10. 10. 10 Mobile Services 1GB SQL From WA Free Trial Database No SLA during Preview. Only small instances available. Can upgrade to a reserved instance at 33% discount from normal Pay-As-You-Go rates during Preview.
    11. 11. 99.9%
    12. 12. Tutorials - Mobile Services Developer Portal Reference and Android 28
    13. 13. Build apps on Windows. Discover your newhome.
    14. 14.