Download to read offline
Uploaded byAlexandre Marreiros
GWAB Mobile Services
The document provides an overview of Windows Azure Mobile Services, outlining its role as a backend-as-a-service for mobile application development, focusing on data storage, user authentication, and messaging. Key new features include improved mobile service building capabilities, custom API integration, and enhanced support for various mobile platforms. The document also emphasizes mobile services' unique capabilities for managing data access, service monitoring, and integration with identity providers.
More Related Content
Similar to GWAB Mobile Services
More from Alexandre Marreiros
GWAB Mobile Services
- 1. What’s new in WindowsAzure Mobile Services Alexandre Marreiros CTO @ Innovagency Tech Trainer & Speaker as Independent SW Architect as Consultant Teacher @ EDIT Lisboa 29 de Março 2014
- 2.
- 3. Agenda o Mobile ServicesOverview o New Things o Recap o References
- 4.
- 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 ServicesIn 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 ServicesIn the Cloud Identity Structured Storage Messaging Media Unstructured Storage Additional Services
- 8. Windows Azure MobileServices ttp://aka.ms/mobileservices
- 9. Windows Azure MobileServices Mobile Client Support IOS, Android, Windows Phone
- 10. Auth* Authenticate against WindowsLive, 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 strengthsof 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)
- 12.
- 13.
- 14.
- 15.
- 16. New to MobileServices
- 17.
- 18. Build and upgradeMobile Services on your enviroment Test and run your future Mobile services definitions and code in your machine
- 19. Use extra modules Youcan 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 MobileServices to create to put in the cloud your one API, based on: - Controller MindSet - HTTP Methods
- 21. Costum API How tocall the api: https://<service_name>.azure-mobile.net/api/<api_name> Examples of API costumization
- 22.
- 23. Source Control conection Inpreview for now You can directly connect your mobile services to your GIT repository
- 24.
- 25.
- 26. Windows Azure MobileServices Client Support IOS, Android, Windows Phone
- 27. Windows Azure MobileServices ttp://aka.ms/mobileservices
- 28.
- 29. Mobile Services Capabilitiesmakit 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 Capabilitiesmake 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.
- 31.
- 32. References http://aka.ms/mobileservices http://pluralsight.com/training/Courses/TableOfContents/windows-azure-mobile- services Windows Azure MobileServices book, Bruce Johnson Windows Azure Mobile Services Concepts (http://msdn.microsoft.com/en- us/library/windowsazure/jj591475.aspx ) Mobile Services Team blog http://blogs.msdn.com/b/azuremobile/
Editor's Notes
- #11 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:
- #12 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:
- #13 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:
- #14 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:
- #15 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:
- #16 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:
- #23 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: