Choosing the right mobile architecture

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. |

Choosing the Right Mobile Architecture

Lonneke Dikmans Managing partner and Oracle Ace Director eProseed NL June, 2015


IntroducLon • About me – Managing partner at eProseed – Oracle Ace Director, working with Oracle tooling since 1998 – Author of SOA Made Simple – Started out as a user experience consultant with a tablet avant la leSre – Experience as a soluLon architect with Mobile architecture in different contexts

• About eProseed – HQ in Luxemburg – Local offices in several parts of the world – Award winning Oracle partner

2


Agenda

Three types of mobile architecture

Overview of MAF

Impact on your Services

Security consideraLons

Scalability

Three use cases

1

2

3

4

5

6

3


•  NaLve Apps • Web App

4

•  Hybrid

Mobile architecture types

Device

OS

The App

Device

OS

The App

Browser

Device

OS

The App

NaLve wrapper app

Embedded Web Views

NaLve UI Views

NaLve hardware access


Hybrid applicaLons

5

Web Views HTML, CSS, Javascript

NaLve PorLon

Rendering Engine

Mobile OS Touch Screen

GSM network

Microphone

Speaker

Camera

VibraLon

Accelerometer, Compass

GPS

Storage

Wifi API calls

API calls

API calls Cordova

OS Specific AP

Is

Device Features

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. | 6

Example AllRecipes.com NaLve app Web

app


Of mobile applicaLons will be hybrid by 2016 Source: Gartner

7

>50%


•  Resides on the device •  ‘App store’ •  NaLve views (per plagorm and version)

•  Access to all device features

•  Offline and online

Oracle ConfidenLal – Internal 8

Mobile architectures

NaLve WebApp Hybrid

•  Resides on Server •  URL •  Browser, in dependent of plagorm or version

•  Limited access to device features

•  Online only

•  Device & Server •  ‘App store’ •  Embedded browser + naLve views

•  Access to all device features

•  Online and offline


Program Agenda with Highlight

Three types of Mobile Architectures

Overview of MAF



Scalability

Three use cases

1

2

3

4

5

9

6


Overview of MAF

10


Of mobile applicaLons will be hybrid by 2016 Source: Gartner

11

>50%




Overview of MAF



Scalability

Three use cases

1

2

3

4

5

12

6


Impact on your services • Protocol • Granularity • Reuse versus specific services

13


•  Based on operaLons •  Described by a WSDL

•  Coarse grained •  Security like a

webapp + message

•  Plagorm and language agnosLc


Protocol

SOAP REST -‐ XML REST -‐ Jason

•  Based on objects •  Described by WADL

•  Fine grained •  Security like a regular webapp

•  Plagorm and language agnosLc

•  Based on objects •  Described by WADL

•  Fine grained •  Security like a regular webapp

•  Plagorm agnosLc, language specific (JS)

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. | eProseed ConfidenLal – Internal/Restricted/Highly Restricted 15

Granularity of services


Services design •  Form factor – Tablet versus smart phone versus google glass versus watch versus …. – ResoluLon

• Context – On route versus staLonary •  Time spent per transacLon

– Hands free or not Using voice and sound versus touch/images and typing

– Online versus offline •  Accessing local or remote data •  UpdaLng the cache

16


Mobile App

• Reuse services: filter data in app

•  Extra Layer of services

17

Service design

PresentaLon services

Services

Mobile App

Customer Employee Expense

Desktop Tablet

Filter

Customer Employee Expense

Desktop Tablet App

Filter




Overview of MAF



Scalability

Three use cases

1

2

3

4

5

18

6


Security consideraLons • Data security – Data on the device should be secure – Malicious apps should not be able to access corporate secured data

• Network security – EncrypLon during transport

• Mobile device Management versus Mobile ApplicaLon Management •  Server side management – AuthenLcaLon and access – Managing services

19


•  Secure Device password •  VPN between device and enterprise server

•  Wipe enLre device

•  Track device •  NaLve and Hybrid •  Dedicated devices



MDM MAM Service Management

•  Secure container password •  Secure container AppTunnel

•  Wipe applicaLon

•  Track applicaLon •  NaLve and Hybrid •  BYOD

•  Secure service •  Transport level security using SSL

•  ProtecLon against DoS •  Track service use •  NaLve, Hybrid, Web App

•  BYOD


Oracle Mobile Security

21




Overview of MAF



Scalability

Three use cases

1

2

3

4

5

22

6


Scalability •  IntroducLon of mobile devices leads to a huge increase in load – Bank apps to check balance – Travel apps to check flight Lmes

•  Several soluLons – Cache responses •  Device •  API manager or Service Bus •  Database

– Load balance services – Smaller services (less data) for mobile use

23




Overview of MAF



Scalability

Three use cases

1

2

3

4

5

24

6

Copyright © 2014, eProseed and/or its affiliates. All rights reserved. | Oracle ConfidenLal – Internal 25

Field engineer fixing a smart meter

CharacterisLcs •  Use on route for planning the trip

•  On site to record acLviLes •  Online and offline in certain areas there is no network available

•  Dedicated device •  Moderate security demands

Benefits

SoluLon •  NaLve app (single purpose device, offline usage important) •  Using exisLng services in back end (filtering can be done in naLve app) •  Mobile Device Management

•  Simple security model: enLre device can be wiped •  Caching of data in local database •  Use all device features like locaLon, contacts etc.


Judge reading court files

Challenge •  Bring your own device •  Tablet to read documents •  Mostly online •  Security demands are high

Benefits

SoluLon •  Hybrid app for a selected set of mobile devices •  Mobile device management (MAM would have been beSer) •  PresentaLon services for mobile

•  Track device •  Wipe device •  Reuse web views for desktop/laptop/tablet


Engineer looking for a new temp job

Challenge •  On route all the Lme •  Mobile device •  Connected •  Low security

Benefits

SoluLon •  Web app •  OAuth •  PresentaLon services for different form factors

•  MulLple plagorm support is easy with web apps •  Low security demands, no need to wipe applicaLons or devices •  Other people can create apps with presentaLon services


•  Mobile architecture –  NaLve versus Web app versus Hybrid –  Depends on device features needed –  Depends on connecLvity demands –  Logic resides on server or on device or both

•  Services –  Protocol (SOAP versus REST) –  Extra layer to expose to mobile or reuse exisLng services

–  Service management

28

•  Security – MDM versus MAM –  IntegraLon with IDM –  Service Management

•  Scalability –  Cache responses –  Scale out services –  Create specific smaller service to decrease load

Summary


QuesLons?

29