Upload
vitor-meriat
View
184
Download
0
Embed Size (px)
DESCRIPTION
Apresentação realizado para o Azure Summit Brasil 2014. http://www.azuresummitbrasil.com.br/2014/
Citation preview
AUDITÓRIO 1
DESENVOLVIMENTO
Palestrante
Azure Mobile Services - Adicione Serviços para suas Aplicações Mobile
Vitor Meriat@vitormeriat
vitormeriat.com.br
Agenda•Qual o porquê do MAMS•Arquitetura do MAMS•Demos, demos, demos ;)
Dispositivos
2003 201
0 2015 202
0
50 bilhões
Cisco
Uma pergunda para você…Qual dispositivo você usa?
Diversos dispositivos, diversas plataformas
Experiência continuada
WindowsPhone 8
iOS AndroidWindows 8Windows 8 AndroidBrowser
Interoperável
Azure Mobile Service
Backend-as-a-Service
consumir
BaaSPlatform-as-a-Service
construir
PaaSInfrastructure-as-a-Service
servir
IaaSSoftware-as-a-Service
consumir
SaaS
Azure Mobile Services
Um backend para todos os seus dispositivosSDKs para Windows, Windows Phone, iOS, Android, Cordova, e XamarinBackends suportados em .NET ou JavaScript
Armazene dados na nuvemUsando SQL Database ou outros backends como Azure Tables Storage e Mongo DB
Autentique seus usuáriosFacebook, Twitter, Microsoft Account, Google, e AAD
Push notificationsSuporte para cross-platform, baixa latência e notificações push em massa com os hubs de notificação
Azure Mobile Service
Push Notifications
Data Storage
User Authentication
SQL Table Storage
Blob Storage
WNS & MPNS
APNS GCM
Mongo DB
Notification Hubs
Facebook Twitter Microsoft Google Azure Active Directory
Windows Store iOSAndroid XamarinPhonegapSencha
Windows PhoneiOSAndroidHTML 5/JS
SDKs
REST
API
Hybrid Connections
Arquitetura MAMS
Node.js Express
.NET Web API
Source Control
Tipos de Backend
ASP.NET Web API
Data Auth Push ToolingBased on Web APISupports various data stores:• Azure databases• SQL server on-prem/IaaS• Table Storage• MongoDB
• Facebook• Twitter• Google • Microsoft Account• AAD
Uses Notification Hubs integration for high-scale, cross-platform push
• 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
.NET Mobile Service Backend
Modelo de dados (“brownfield”)
TableController
DomainManagerDTO
DTO
Mobile ServiceDevice
Model
AutoMapper
SQL Azure/BYOD
ExistingTables
SystemPropertiesTable
Novo modelo de dados (“greenfield”)
TableController
DomainManagerDTO
DTO
Mobile ServiceDevice
SQL Database
BYOD
MongoDB
Table Storage
Suporte ao modo Offline
Mobile ServiceTable ControllersDevice
SQLite
Explicit Push/PullCUD order preserved
Conflict resolution
SQL Database
BYOD
MongoDB
Table Storage
DTO Model
Mapping
1. App registers with provider2. App gets token3. App sends token to backend4. Push requested5. Backend delivers push to provider6. Provider pushes to device
PlatformNotification
Service
App back-end
Push Notification – Ciclo de vida
One-time set up1. Create a Notification Hub
Register2. The client app retrieves its current handle from the PNS3. Client app creates (or updates) a registration on the Notification Hub
with the current handle
Send Notification4. The app back-end sends a message to the Notification Hub5. Notification Hub pushes it to the PNS’
APNsWNS
Notification Hub
App back-end
iOS app Windows app
MPNS
GCM
ADM
Notification Hubs
Notification Hubs
WindowsPhone 8
iOS AndroidWindows 8 Kindle
Demonstração
Documentation resourceReference: http://msdn.microsoft.com/en-us/library/jj554228.aspx
REST API for all platformsReference: http://msdn.microsoft.com/en-us/library/jj710108.aspx
ALL librarys Nuget package: https://nuget.org/packages/windowsazure.mobileservices GitHub: https://github.com/Azure/azure-mobile-services Client SDKs and Samples for Azure Mobile Services: http://azure.microsoft.com/en-us/develop/mobile/
Mobile Services APIs and SDKs
AUDITÓRIO 1
DESENVOLVIMENTO
Palestrante
Obrigado!!!
@vitormeriat
vitormeriat.com.br
Vitor Meriat
Obrigado por sua presença.