The emerging enterprise mobile cloud platform

Speaker: Mike Keith, Jason Haley

Mobile Cloud Service

• Mobile Backend as a Service
• one device to rule them all
• devices are specialized to do specific things: but we expect to be general purposes!!!!

Challenges of enterprises: they wants to let their application to be used via mobile

• Backend Integration/Federation (databases)
• Channel security (MAM, MDM, API, OAuth, ...): biggest concern which have all the enterprises
• Client-side development (device to support???)
• Delivery & Organization challenges (how to provide/release apps?)
• An important aspect is the T2M (time to market) and the platform should provide that

Differences from application types

• B2C
• masses application
• no control on the device
• no profile/user required, in case self registration
• B2E
• limited number of clients
• BYOD, or managed devices
• MAM or MDM
• complete user profile Idm from company
• sensitive data

See the platform

(picture)

API Management
Controlling access to data assets

Separate APIs (interfaces= from implementation.

• Define definition language for API
• The API Manager allows to upload these language spec in the module
• then also the implementation is required
• API Manager supports also auth & autz
• API catalog is provided also
• Gives a view about how and who is calling the APIs
• provides also monitoring and measurement tools

MBaaS: the next step

The platform

• Channel: different devices and vendors to support
• The sdk provided supports that.
• The mobile cloud service act also as the responsible for integrate to external apps or other system in general
• The platform provide so called connector to be able to connect to any data anywhere.

• problem with data service which need sessions! and the session need to be stick to the mobile device as well

Push notification

• Needs to be integrated with native platform. create an abstract layer cross provider.
• Ability to push notification to a group of people based on generic criteria

Analytics

• how to know who and how an app is used
• two types provided by the platform:
• System analytics
• Application analytics

User Management

• Allows to manage users and roles in the system
• Declarative/Programmatic approach

Storage

• Object storage: key-value store (blogs, json)
• possible to query the json
• Database storage: 
• classical db service
• limit client access

Custom code

• allows to inject all personal functionality in the MBaaS
• can invoke any service introduced before
• supports more language (Java, Ruby, ...)

Geo-Location

• API to provide geo location of the device
• locality can be a very added value to several business domain

PSR

• Performance Scalability Reliability

Tools

• agnostic. allowed to use Git, 

Security 

• Authentication using OAuth2
• token can expire
• Role-based API security
• key and certificate management
• SSL for all device to platform transport

Demo time: creating a new API

Nice to see platform. Everything or most of it is done in declarative way