Starting Azure mobile services

Editor's Notes

• #4: Speaking Points: There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc. Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices. The cloud can help deliver IT as a standardized service…freeing you up to focus on your business
• #5: Slide Objectives: Explain the three established industry terms for cloud services Speaker Notes: There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service. Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform. Notes: There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services. The industry has defined three categories of services: IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another.
• #10: Slide Objectives: Detail the differing compute options and scenarios where each would be used
• #13: 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:
• #16: 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
• #17: 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
• #18: Slide Objectives: Outline the Key Scenarios Mobile Services can be used for
• #19: Things to note Connection string/application key Data (nothing there to start) authentication
• #20: Slide Objectives: Jump to VS and Demo the New Mobile Service Create a new Windows 8 application experience in the portal
• #21: Create a table Generate ToDoItem table (simplifies the demo) Show the cloud icon Things to show Records (will come to that soon) Scripts authentication
• #22: - 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
• #23: 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.
• #24: Slide Objectives: Explain how Windows Azure websites are simple, easy, and open. Notes:
• #25: Git Deployment is Native, or through a Service hook from CodePlex, GitHub or BitBucket
• #26: 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
• #27: 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
• #28: 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:
• #29: 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:
• #30: 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.
• #31: 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
• #32: 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
• #34: 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
• #38: Speaking Points: All of the features I demoed today are available now either in released or preview form. The services that had the preview tag next to them in the management portal are currently in preview mode, meaning that they are not yet final. These services will be coming out of preview next calendar year. Working hard on getting them done as soon as possible. If you haven’t gotten started yet with Windows Azure, I encourage you to go to WindowsAzure.com and sign-up for an account. If you have an MSDN subscription you can activate up to $3700 worth of yearly Windows Azure benefits. Otherwise you can sign-up for a free trial and get started.