Mobile Offline OData Framework for Azure
Download as PPTX, PDF1 like1,537 views
This document discusses mobile offline frameworks and patterns. It outlines how offline capabilities were traditionally implemented using database and file synchronization but that REST, SOAP, and caching are now more common approaches. The document analyzes examples of using different patterns for short messages, large files, and recent customer projects. It proposes an offline framework for Azure that leverages OData synchronization for databases and files as well as an offline message queue.
Mobile Offline OData Framework for Azure
- 1. MOBILE OFFLINE FRAMEWORK FOR AZURE Paul Zhou
- 2. AGENDA Background Is Mobile Offline Feature the Niche? Framework to support Mobile Offline Apps
- 3. MOBILE APP OFFLINE PATTERNS RDB synchronization File synchronization Message Queue RPC
- 4. Mobile Device Server Handheld Application DB Sync Engine Publications & Subscriptons RDBMS Small Footprint RDBMS DB Sync Engine RDB SYNC
- 5. FILE SYNC
- 8. OLD DAYS No(Expensive) Cellular Data Expensive Mobile Devices Business Data Exchange Scenario Work start in office : sync Do the work during the day without syncing Back to office: sync Offline Patterns: RDB Sync and File Sync Windows Solution(Merge and SyncFramework), Sybase Ultralite solution
- 9. THINGS HAVE CHANGED Cheap Cellular Data Cheap Mobile Devices Business Data Exchange Scenario Any time Offline Patterns: REST, SOAP and Caching iOS device, Android Device
- 10. IS OFFLINE STILL RELEVANT? Availability: Some areas, locations have no connection Performance Unstable connection drags performance Reliability Losing data is evil
- 11. HOW OFFLINE ARE OUR RECENT CUSTOMER PROJECTS? CP: 100% ALC: 100% PK: 100% SIT: 70% TF: 10% OCT: 10% GI: 10% SSI 10% CAUBO 10% OCDSB 0%
- 12. EXAMPLE1- SHORT MESSAGE(GPS COORDINATE) DB and synchronization Store GPS coordinates in a table and do background sync File and Synchronization Store GPS coordinates in a file and do background sync Message Queue Put coordinates in a local queue RFC(REST/SOAP) and Caching Send coordinates when connection available Cache when fails: file, dictionary, sqlite Send caches when connection available again
- 13. EXAMPLE2- BIG FILES(PHOTO) DB and synchronization Store file in a table and do background sync File and Synchronization Store file locally and do background sync Message Queue Not applicable RFC(REST/SOAP) and Caching Send file when connection available Store locally when fail Send file again when connection available
- 14. EXAMPLE3: RECENT PROJECTS CP/ALC/….(Windows Mobile) DB Sync OCT (iPhone) REST+JSON and SQLite caching GI REST+JSON and SQLite caching PC REST+JSON and SQLite and files SSI/CAUBO SOAP+XML and Dictionary serialization ShiftIT REST+JSON and SQLite caching Touch Fleet REST+JSON
- 15. ODATA SYNC FOR RDB
- 16. ODATA SYNC FOR FILES