Academic journal article Informatica Economica

NoSQL and SQL Databases for Mobile Applications. Case Study: MongoDB versus PostgreSQL

Academic journal article Informatica Economica

NoSQL and SQL Databases for Mobile Applications. Case Study: MongoDB versus PostgreSQL

Article excerpt

Compared with "classical" web, multi-tier applications, mobile applications have common and specific requirements concerning data persistence and processing. In mobile apps, database features can be distinctly analyzed for the client (minimalistic, isolated, memory-only) and the server (data rich, centralized, distributed, synchronized and disk-based) layers. Currently, a few lite relational database products reign the persistence for client platforms of mobile applications. There are two main objectives of this paper. First is to investigate storage options for major mobile platforms. Second is to point out some major differences between SQL and NoSQL datastores in terms of deployment, data model, schema design, data definition and manipulation. As NoSQL movement lacks standardization, from NoSQL products family MongoDB was chosen as reference, due to its strengths and popularity among developers. PostgreSQL serves the position of SQL DBMSs representative due to its popularity and conformity with SQL standards.

Keywords: Mobile Applications, NoSQL, SQL, PostgreSQL, MongoDB

1 Introduction

"Mobile world" is one of the most dynamic areas of Information Technology today. Smartphones and tablets explosion have created a huge market for mobile applications. Consequently there is an increasing demand for mobile application developers so that, even when taking into account just the case of Romania, many books [1] [2] [3] and articles (e.g. [4], [5], [6], etc.) have been published. Also many Business Information Systems/Business Informatics undergraduate and master programs introduced in their curriculum courses related to mobile devices and applications (e.g., curriculum_2012_2014.jsp,, http ://www. econ.ubb aster_2012_2013/E-Business.pdf).

Almost all of the mobile applications require a persistent data layer, including options for queries. So the interest of database professionals, academics and researchers for mobile technologies is increasing. Mahmoud et al. [7] even suggest including mobile storage topics, devices and applications into database courses.

This paper presents technologies and tools for deployment of the data layer in mobile applications on some major platform focusing on a NoSQL datastore, MongoDB. Section 2 deals with some specific requirements of mobile software in terms of storage and databases. Section 3 deepens the discussion of data storage features for major mobile platforms. The arguments for a NoSQL solution, including a basic description of mobile cloud solution implemented in MongoDB are subjects of section 4. Sections 5, 6 and 7 analyse some of the main differences in terms of database schema, Data Definition Language (DDL), Data Manipulation Language (DML) and database query between SQL (PostgreSQL dialect) and MongoDB.

2 Common Issues of Mobile Applications Storage Layer

Mobile applications share many features of "classical" client/server or web multi-layered applications architecture. Figure 1 depicts a classical six-layered (Security layer covers all the other five layers) framework [8] for enterprise mobile application development.

Persistence layer have similar requirements in terms of storage, DDL, DML and database query. Also the data accessibility mechanisms from application layers are similar to other web applications.

The most striking difference between mobile and web application databases concerns is that while server persistence layer is similar, the client platforms of mobile apps (running mainly on smartphones and tablets) have a smaller scale of available resources (memory, processing power). Many mobile applications require replication and synchronization mechanisms for data persistent on smartphone with a centralized large scaled database available on a server [9] [10], Data storage for client must be processed without hard disk techniques [11] [12],

Nori [13] identifies 11 characteristics that have to be provided, partially or fully, by the mobile and embedded DBMSs:

a. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.