Azure Mobile Sites What it is and What's new as a session i had made at the Global Windows Azure Bootcamp 2014 in Microsoft Portugal.
The Main propouse of this presentation was to show how mobile services can be a good choice, how to use, and what's the state of the art
[2024]Digital Global Overview Report 2024 Meltwater.pdf
GWAB Mobile Services
1. What’s new in
Windows Azure
Mobile Services
Alexandre Marreiros
CTO @ Innovagency
Tech Trainer & Speaker as Independent
SW Architect as Consultant
Teacher @ EDIT
Lisboa
29 de Março 2014
5. Intro
“Building a robust, modern mobile application often requires a developer to
not only focus on the front end user experience, but also backend services
such as data storage, user authentication, and often push notification
services.“
“Windows Azure Mobile Services provides a scalable and easy-to-use
„backend-as-a-service‟ ”
6. Backend Mobile Services In the
Cloud
Mobility Cloud
Sometimes Computional Limited Computional Limitless
Almost no Storage Conceptual Unlimited Storage
Rapid Growing Scale / Elastic
Conect everywhere Services via internet
Desires a Simple Computational Model Scale and Elastic
7. Backend Mobile Services In the
Cloud
Identity
Structured Storage
Messaging Media
Unstructured Storage Additional Services
10. Auth*
Authenticate against Windows Live, Twitter, Facebook, …
Table level permissions for each CRUD operation
Everyone
Anyone with the Application Key (NOT A SECURITY TOKEN/CONTROL Hint that user is
coming from your app (reduce chance of misuse))
Only Authenticated Users
Only Scripts and Admins
More granular control with server side scripts
user.level: {admin, authenticated, anonymous}
user.userId: id or undefined if not authenticated
11. Data Storage
Leverage strengths of Windows Azure SQL Database
New or Existing Database
Reporting, TSQL support, existing tools, etc.
Manage your way (portal, REST API, SSMS, etc.)
Partition applications by schema
App1.Users
App2.Users
Dynamic Schema Support (on/off)
18. Build and upgrade Mobile Services
on your enviroment
Test and run your future Mobile services definitions and code in your machine
19. Use extra modules
You can add extra
functions to base
Mobile services based
on 3rd party market
resellers
example:
Use New Relic to have
insights about hows
services on azure are
performing
20. Costum API
Use Mobile Services to create
to put in the cloud your one
API, based on:
- Controller MindSet
- HTTP Methods
21. Costum API
How to call the api:
https://<service_name>.azure-mobile.net/api/<api_name>
Examples of API costumization
29. Mobile Services Capabilities makit
unique
Precise control for authorizing access to tables.
Supports scripts to inject business logic into data access operations.
Integration with other cloud services.
Supports the ability to scale a mobile service instance.
Service monitoring and logging.
30. Mobile Services Capabilities make
him unique
Client libraries support mobile app development on various devices, including
Windows 8, Windows Phone 8, iPhone, and iPad.
Simple provisioning and management of tables for storing app data.
Integration with notification services to deliver push notifications to your app.
Integration with well-known identity providers for authentication.
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 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 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 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 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 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 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: