*Result*: NoSQL and SQL Databases for Mobile Applications. Case Study: MongoDB versus PostgreSQL.
*Further Information*
*Compared with "classical" web, multi-tier applications, mobile applications have common and specific requirements concerning data persistence and processing. In mobile apps, data-base 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 stor-age options for major mobile platforms. Second is to point out some major differences be-tween SQL and NoSQL datastores in terms of deployment, data model, schema design, data definition and manipulation. As NoSQL movement lacks standardization, from NoSQL prod-ucts family MongoDB was chosen as reference, due to its strengths and popularity among de-velopers. PostgreSQL serves the position of SQL DBMSs representative due to its popularity and conformity with SQL standards. [ABSTRACT FROM AUTHOR]
Copyright of Informatica Economica is the property of Informatica Economica and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)*