Mobile Databases - York University

Mobile Databasesby Niloofar BanivahebPowerpoint TemplatesPage 1

Why Mobile Databases? Number of smartphones in use around the worldpassed 1 billion in 2012. Next billion devices could be reached within lessthan three years. More businessesmobility.movetowardemployees Powerful lightweight computing devices and lowcost mobile connectivity paved the way fordata-driven applications.Powerpoint TemplatesPage 2

Why Mobile Databases? Mobile data-driven applications enable us to accessany data from anywhere, anytime. Examples: Salespersons can update sales records on the move. Reporters can update news database anytime. Doctors can retrieve patient’s medical history fromanywhere. Mobile DBMSs are needed to support these applicationsdata processing capabilities.Powerpoint TemplatesPage 3

Mobile Database: A mobile database is a database that can be connectedto by a mobile computing device over a wirelessmobile network. Mobile databases: Physically separate from the central databaseserver. Resided on mobile devices. Capable of communicating with a central databaseserver or other mobile clients from remote sites. Handle local queries without connectivity.Powerpoint TemplatesPage 4

Client-Server Mobile Databases:MobileDBCentralServerLaptopMobile DBMSCentralDatabaseCentralDBMS Mobile DBMSMobileDBPowerpoint TemplatesSmartphonePage 5

Client-Server Mobile Databases: Client-server modelinformation systems.isthetraditionalmodelof It is the dominant model for existing mobile databases. The server can become a single point of failure andperformance bottleneck. Even storing data on a cluster of machines to backupcentral database might cause performance bottleneckand data inconsistency.Powerpoint TemplatesPage 6

Peer-to-Peer Mobile Databases:MobileDBLaptopTabletMobileDBMobile DBMS Mobile DBMSMobile DBMSMobileDBPowerpoint TemplatesSmartphonePage 7

Peer-to-Peer Mobile Databases: In P2P mobile databases, the database maintenanceactivities are distributed among clients. Every process plays part of the role of the server,besides its client role. A client that wants to access a piece of data, sends arequest to other peer clients and they forward therequest until the data is found. The major problem in this model is ensuring theavailability of data .Powerpoint TemplatesPage 8

Characteristics of Mobile Environments:Why not use an appropriate existing model ofdatabases in a mobile environment? Characteristics of mobile environments: Restricted bandwidth of wireless networks. Limited power supply. Limited resources. Mobility. Disconnections.Powerpoint TemplatesPage 9

Current Approach: Currently most mobile application developers use “flatfiles” to store application data. A “flat file” is a file containing records that have nostructured interrelationship. Advantages:Smaller and easier to manage. Disadvantages:Applications need to know the organization of therecords within the file.Developers have to implement the required databasefunctionalities.Powerpoint TemplatesPage 10

Requirements of Mobile DBMSs: Mobile DBMSsrequirements :shouldsatisfythefollowing Small memory footprint. Flash-optimized storage system. Data synchronization. Security. Low power consumption. Self-management. Embeddable in applications.Powerpoint TemplatesPage 11

Small Memory Footprint: Memory footprint is amount of mainmemory that an application uses whilerunning. Mobile devices have limited memory, sothe mobile database application shouldhave a small footprint. The size of mobile database affects the overallapplication footprint . Mobile DBMSs should be customizable to include onlythe required database functionalities.Powerpoint TemplatesPage 12

Flash-Optimized Storage System: Flash memories are dominant storage devices forportable devices . They have feature such as: Small size.Better shock resistance.Low power consumption.Fast access time.No mechanical seek and rotational latency. Mobile DBMSs need to be optimized to exploit theadvantages of the new storage devices.Powerpoint TemplatesPage 13

Data Synchronization: Portabledevicescannotconnected all the time.stay Users can access and manipulatedata on their devices. They are also unable to store a large amount of datadue to lack of storage capacity. Mobile DBMSs should have the synchronizefunctionality to integrate different versions of data intoa consistent version.Powerpoint TemplatesPage 14

Security: Security is very important for data-centricmobile applications. It is more important when the applicationworks with critical data that its disclosureresults in potential loss or damage. Data that are transmitted over a wireless network aremore prone to security issues. Mobile DBMSs should implement a complete end-toend security to ensures the secure transfer of data.Powerpoint TemplatesPage 15

Low Power Consumption: Portable devicessupplies.havelimitedpower Battery life of mobile phones is expectedto increase only 20% over the next 10years. Processor, display and network connectivity are themain power consumers in a mobile device. Mobile DBMSs need to be optimized for efficient powerconsumption.Powerpoint TemplatesPage 16

Self-Management: In traditional databases, the databaseadministrator (DBA) is responsible fordatabases maintenance. In mobile DBMSs there can be no DBA tomanage the database. Mobile DBMSs need to support self-management andautomatically perform the DBA tasks. Some mobile DBMSs allow remote management thatenables a DBA to manage the mobile databases from aremote location.Powerpoint TemplatesPage 17

Embeddable in applications : Administrators does notaccess to mobile devices.havedirect Mobile DBMSs should be an integral partof the application that can be delivered asa part of the applications. The database must be embeddable as a DLL file in theapplications. It must be also possible to deploy the database as astand-alone DBMS with support of multiple transaction.Powerpoint TemplatesPage 18

Existing Mobile Databases: Mobile databases: Sybase SQL Anywhere Oracle Lite Microsoft SQL Server Compact SQLite IBM DB2 Everyplace (DB2e) Embedded database: TinyDB PicoDBMSPowerpoint TemplatesPage 19

Sybase SQL Anywhere: Initially created by Watcom as Watcom SQL. SQL Anywhere was launched in in 1995. It dominates the mobile-database field, withabout 68% of the mobile database market. Database files are independent of the operating systemand transferable between supported platforms. Strong encryption is supported for both database filesand client-server communication.Powerpoint TemplatesPage 20

Oracle Lite: Omniscience Object Technology, Inc. wasacquired by Oracle Corporation in November1996 . Their product (Omniscience ORDBMS) became the firstversion of Oracle Lite. Oracle Lite runs in under 1 MB of memory, and can beinstalled in 3 MB of hard disk space. Personal Oracle Lite (POL) is a lightweight, single-userrelational database that runs on desktops, laptops,down to the smallest hand help devices.Powerpoint TemplatesPage 21

Microsoft SQL Server Compact: Formerly known as SQL Server MobileEdition. SQL Server Compact is free to download andredistribute. It is optimized for an architecture where all applicationsshare the same memory pool. SQL CE runs in-process with the application which ishosting it. It has a memory footprint of approximately 5 MB anddisk footprint of less than 2 MB .Powerpoint TemplatesPage 22

SQLite: SQLite is an open source mobile databaseengine. It is a server-less database engine thatneeds zero-configuration. SQLite is a popular choice as mobile database for localstorage in mobile applications. SQLite engine has no standalone processes with whichthe application program communicates. SQLite implements most of the SQL-92 standard.Powerpoint TemplatesPage 23

IBM DB2 Everyplace: DB2e has been discontinued and April 2013is the end of support date. It had the biggest market share after SQLAnywhere. It had the smallest memory footprint (350 KB) incompare to other commercial mobile databases. IBM has replaced DB2e with IBM solidDB family. SolidDB is a in-memory MDBMS with robust datacatching features.Powerpoint TemplatesPage 24

Embedded Databases: Embedded database systems are tightly integratedwith an application that requires access to stored data. They are hidden from the application’s end-user andrequires little or no ongoing maintenance. Embedded databases need less resources in comparewith mobile databases. They are optimized for specific devices such assmartcards and sensors. They support limited and specified functionalities ofthe standard SQL.Powerpoint TemplatesPage 25

PicoDBMS: PicoDBMS only supports sufficient functionalities forsmartcard applications. Smartcard applications are used for data managementsuch as insert, delete, update and search. PicoDBMS supports a part of SQL: INSERT, UPDATE, DELETE, SELECT CREATE/DROP TABLE/VIEW GRANT/REVOKE Footprint size of PicoDBMS is about 30KBytes.Powerpoint TemplatesPage 26

TinyDB: TinyDB has been developed at University of Berkeley. It supports only essential functionalities for sensorapplications. Most of the sensor applications are used to filter outsome data so they just need to select data with givenconditions. TinyDB supports only SELECT operation of thestandard SQL. Its memory footprint is only 3KBytes.Powerpoint TemplatesPage 27

Comparison:Target DevicesMobile DBMSsExtremely SmallDevices with LowComputing PowerSensorsTinyDBSmartcardsPicoDBMSSmall Devices withHigh ComputingPowerCell Phones,PDAs, CarNavigators,Ultra BooksSybase SQL Anywhere,Oracle Lite,MS SQL Server CE,SQLiteIBM DB2 EveryplacePowerpoint TemplatesPage 28

Functionalities:TinyDBPicoDBMSOracleLiteIBMDB2eMS SQL ServerCompactMinimumFootprint Size3 KB30 KB970 KB320 KB2 MBSQLSELECTonlya part ofSQL99a part ofSQL99a part ofa part of currencyNNYYYIndexingNYYYYEncryptionNN/AYYYAccess ControlNYYYYPowerpoint TemplatesPage 29

Supportability of MDBMS Requirements:TinyDBPicoDBMSOracleLiteIBMDB2eMS SQL ServerCompactSmall FootprintYYYYYFlash-OptimizedStorage YYN/AYN/ALow PowerConsumptionYYNYYSecurityNYYYYPowerpoint TemplatesPage 30

References:1.Nori, A. Mobile and embedded databases. In Proc. SIGMOD 2007,ACM Press (2007), 1175-1177.2.Tsiftes, N. and Dunkels, A. A database in every sensor. In Proc.SenSys 2011, ACM Press (2011), 316-332.3.Whang, K.Y., Song, I.Y., Kim, T.Y., and Lee, K.H. The ubiquitousDBMS. ACM SIGMOD Record 38, 4 (2009), 14-22.4.Sen, R. DBMS techniques for lightweight computing devices. InProc. MobiDE 2011, ACM Press (2011), 1-8.Powerpoint TemplatesPage 31

Thank YouPowerpoint TemplatesPage 32

Powerpoint Templates Page 4 Mobile Database: A by mobile database is a database that can be connected to a mobile computing device over a wireless mobile network. Mobile databases: Physically separate from the central database server. Resided on mobile devices. Capable of communicating with a central database server or