1.
Mobile Sync Cloud <ul><li>Alejandro M. Ramallo - Group Head of Technology, BAT </li></ul><ul><li>Phil Shotton - Cloudscape </li></ul>

2.
Background <ul><li>The MARTINI Project is a global initiative to provide a flexible, extensible TM&D system </li></ul><ul><li>A System-of-systems (SOA) aimed at replacing the existing regional/local solutions. </li></ul><ul><li>More than 10,000 Sales Reps worldwide will use hand-held devices (Smart-phones, PDAs etc) to manage sales fulfilment and order delivery functions </li></ul><ul><li>The hand-held will run a bespoke application accessing a local database holding an extract from the BAT backend’s master database </li></ul>

3.
Objectives <ul><li>Robust, resilient synchronisation capability </li></ul><ul><li>Full database load </li></ul><ul><li>Bi-directional delta synchronisation </li></ul><ul><li>Background scheduling of data retrieval and synchronisation </li></ul><ul><li>Field-level delta updates to minimise network bandwidth requirements and backend system load </li></ul>

4.
Requirements <ul><li>Provide bi-directional, asynchronous, delta synchronisation </li></ul><ul><li>Conflict resolution at field level </li></ul><ul><li>Minimise mobile connect time </li></ul><ul><li>Plug-in architecture, extensible </li></ul><ul><li>Scalability </li></ul><ul><li>Performance </li></ul><ul><li>Hub-and-spoke capabilities </li></ul>

5.
Scale <ul><li>2,500,000 outlets visited every week more than once ~ 4 million visits </li></ul><ul><li>10,000 Sales Reps * 77 Mb per user = 752 Gb </li></ul>

6.
Alternatives considered COTS Bespoke using RDBMS Bespoke Space-based <ul><li>Stateless engine </li></ul><ul><li>State in RDBMS or Queues </li></ul><ul><li>No hub-and-spoke </li></ul><ul><li>High availability is costly </li></ul><ul><li>RDBMS requires administration </li></ul><ul><li>Development platform lock-in </li></ul><ul><li>Not really made for our data volumes </li></ul><ul><li>Stateless engine </li></ul><ul><li>Bespoke caching </li></ul><ul><li>State in RDBMS </li></ul><ul><li>Hub-and-spoke more difficult to implement </li></ul><ul><li>High availability is costly </li></ul><ul><li>RDBMS requires administration </li></ul><ul><li>Development platform lock-in </li></ul><ul><li>Not really made for our data volumes </li></ul><ul><li>100% in-memory </li></ul><ul><li>Distributed </li></ul><ul><li>Partitioning </li></ul><ul><li>Hub-and-spoke </li></ul><ul><li>Cleaner/Better programming model </li></ul><ul><li>Multi-platform support </li></ul><ul><li>Resilience </li></ul><ul><li>Performance </li></ul>

7.
A space-based sync engine

8.
Challenges <ul><li>Data Mapping </li></ul><ul><li>Data extraction, visibility, 'invisible' delete </li></ul><ul><li>Support multiple models simultaneously </li></ul><ul><li>Decouple sync clients </li></ul><ul><li>Memory and Performance requirements </li></ul>

9.
Scale <ul><li>2,500,000 outlets visited every week more than once ~ 4 million visits </li></ul><ul><li>10,000 Sales Reps * 77 Mb per user = 752 Gb </li></ul><ul><li>53 Sales Reps per space @ 4 Gb per space </li></ul><ul><li>188 spaces + backup </li></ul><ul><li>@10 spaces per machine = 38 machines </li></ul>

10.
Design Principles <ul><li>Decompose problem into discrete tasks </li></ul><ul><li>Tasks model process flow </li></ul><ul><li>Pluggable services provide business logic </li></ul><ul><li>Extraction, Upload and Mapping driven by externally-managed configuration </li></ul><ul><li>Highly-scalable, resilient, space-based architecture </li></ul>

11.
High Level Architecture Mobile Software Data Centre ERP Services Service Bus Space Bus (Hub) Messaging Bus CRM Sync Engine Space Bus (Spoke) Sync Engine Mobile Software WAN Sync Gateway

12.
High Level Architecture

13.
Internal Architecture

14.
Downward flow

15.
Upward flow

16.
Backend extract

17.
Reconciliation

18.
Backend upload

19.
Lessons learned <ul><li>GigaSpaces can be used to create a Mobile Data Cloud </li></ul><ul><li>Volumes of scale with resiliency can be achieved </li></ul><ul><li>You are only as fast as your slowest link / bottleneck </li></ul><ul><li>Monolithic Back Office systems present challenges that can be overcome although it would be nice if vendors migrate to SOA (really) </li></ul>

20.
Questions