This document discusses backend-as-a-service (BaaS) and Azure Mobile Services. It provides an introduction to MBaaS and its typical features. It then outlines the features of Azure Mobile Services, including its use of WebAPI and support for .NET development. Finally, it discusses data access and offline support in Azure Mobile Services, including approaches for new ("greenfield") and existing ("brownfield") data models and how offline data is synced.

1. //publish/Let’s Geek Out!
Backend-as-a-Service
Azure Mobile Services

2. Who am I?
{
“name” : “Sandeep Joshi,
“company” : “almpeople”,
“userType” : “enthusiastic”
“technologies” : [ “.NET”, “Azure”, “Web”, “Mobile”, “Cloud” ],
“w8experience” : [ “1 LoB App”, “1 Mobile App”],
“blog” : “www.almpeople.com”,
“email” : ”sandeep@almpeople.com”,
“socialMedia” :
{“twitter” : “@sandeepmvp”}
}

3. Agenda
• MBaaS Introduction
• Lap around .NET backend
• Data access and offline support
• Q&A

4. MBaaS Introduction
According to Forrester, MBaaS (Mobile Back end as a service) offerings typically
include:
1. Cloud-based storage for mobile data
2. Ability to automatic generate REST-based interfaces to read and write data
3. Internet optimized data access
4. User/security management tools
5. Usage analytics
security of data in the backend and on the apps
solve hard backend problems for developers Scale across clouds
managing users across identity spaces
flexibility to run custom business logic for your apps anywhere
Not just data backend BUT full-feature backend solution

5. Azure Mobile Services Features
Based on WebAPI

6. •Programming model (data, scheduled jobs)
•Visual Studio tooling
•Local and remote debugging
•Publish
Lap around the .NET backend

7. source
Mobile Services
compatible WebAPI
controllers
git
WebDeploy
Commit hook: Build
project
Website
XDRIVEsitewwwroot
Mobile Services
compatible WebAPI
controllers
Web.config
C:...MobileServices
Mobile Services
runtime
Web.config
website root
load
User database:
EF code-first migrations
or custom migrations
App settings
injected here

8. Data access and offline support

9. New data model (“greenfield”)
TableController
DataManager
DTO
DTO
Mobile ServiceDevice
SQL Database
BYOD
MongoDB
Table Storage

10. Existing data model (“brownfield”)
TableController
DataManager
DTO
DTO
Mobile ServiceDevice
Model
AutoMapper
SQL Azure/BYOD
Existing
Tables
System
Properties
Table

11. Offline support
TableController
(with optimistic
concurrency)
Mobile ServiceDevice
SQL Database
BYOD
MongoDB
Table Storage
SQLite
Explicit Push/Pull
Conflict resolution